Hi All,
Just a FYI, I did an update on a Linux install and wound up with a segmentation fault. Untarring the exec archive did not do the trick.
This is all the data I could come up with, hope it helps. I think it has to be something changed within the last 48 hours.
Starting program: /sbbs/exec/sbbs -nd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Synchronet Console for Linux Version 3.17a Copyright 2015 Rob Swindell
Reading /sbbs/ctrl/sbbs.ini
Program received signal SIGSEGV, Segmentation fault.
memset () at ../sysdeps/x86_64/memset.S:78
78 ../sysdeps/x86_64/memset.S: No such file or directory.
(gdb)
Re: Segmentation Fault
By: Darkages to All on Fri Jan 29 2016 02:18 am
Hi All,
Just a FYI, I did an update on a Linux install and wound up with a segmentation fault. Untarring the exec archive did not do the trick.
This is all the data I could come up with, hope it helps. I think it has be something changed within the last 48 hours.
Starting program: /sbbs/exec/sbbs -nd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1"
Synchronet Console for Linux Version 3.17a Copyright 2015 Rob Swindell
Reading /sbbs/ctrl/sbbs.ini
Program received signal SIGSEGV, Segmentation fault.
memset () at ../sysdeps/x86_64/memset.S:78
78 ../sysdeps/x86_64/memset.S: No such file or directory.
(gdb)
Looks like Deuce committed a fix to CVS already. Sorry about that,
digital man
Synchronet "Real Fact" #72:
SyncTERM (created by Deuce) contains portions of Synchronet and SEXYZ code. Norco, CA WX: 60.2øF, 29.0% humidity, 6 mph W wind, 0.00 inches rain/24hrs
Re: Binkit & Segmentation Fault
By: Ray Quinn to All on Sun Feb 17 2019 09:14 am
I am going to address the segmentation fault first.
After downloading the latest development source on Tursday February 14, 2019 and compiling it, SBBS would not run. I am running Debian Stretch. I tried the GDB method to see about getting a core file, no good.
gdb /sbbs/exec/sbbs /tmp/core.sbbs.0001
What does that mean - no good?
I ran it several times in a console window and got a segmentation fault at various stages.
Try a clean rebuild.
I went to my source backup, compiled it, and all is well. I
likely have no other information to provide. I will try again later today and, if it fails again, get more information.
Run src/cleanall.sh before your next build.
Re: Binkit & Segmentation Fault
By: Ray Quinn to All on Sun Feb 17 2019 09:14 am
I am going to address the segmentation fault first.
After downloading the latest development source on Tursday February 14, 2019 and compiling it, SBBS would not run. I am running Debian Stretch. I tried the GDB method to see about getting a core file, no good.
gdb /sbbs/exec/sbbs /tmp/core.sbbs.0001
What does that mean - no good?
It didn't create any core, it ran as long as it did trying any other method I mentioned.
It didn't create any core, it ran as long as it did trying any other
method I mentioned.
You don't have core files from the previous segfaults? You don't need
to run sbbs from gdb to get a core dump file created upon segfault.
Check your /tmp directory or wherever you have your system configured
to save core dumps.
On 2019 Feb 17 22:41:12, Digital Man wrote to you:
It didn't create any core, it ran as long as it did trying any other
method I mentioned.
You don't have core files from the previous segfaults? You don't need to run sbbs from gdb to get a core dump file created upon segfault. Check your /tmp directory or wherever you have your system configured to save core dumps.
you might have to set your ulimit, too... i've had numerous programs segfault and say a core file was written when in fact none was... setting ulimit as needed allowed the core files to be created properly...
You don't have core files from the previous segfaults? You don't need to run sbbs from gdb to get a core dump file created upon segfault. Check your /tmp directory or wherever you have your system configured to save core dumps.
On 2019 Feb 17 22:41:12, Digital Man wrote to you:
It didn't create any core, it ran as long as it did trying any other
method I mentioned.
You don't have core files from the previous segfaults? You don't need to run sbbs from gdb to get a core dump file created upon segfault. Check your /tmp directory or wherever you have your system configured to save core dumps.
you might have to set your ulimit, too... i've had numerous programs segfault and say a core file was written when in fact none was... setting ulimit as needed allowed the core files to be created properly...
Re: Segmentation Fault
By: mark lewis to Ray Quinn on Mon Feb 18 2019 12:46 pm
On 2019 Feb 17 22:41:12, Digital Man wrote to you:
It didn't create any core, it ran as long as it did trying any other
method I mentioned.
You don't have core files from the previous segfaults? You don't need to run sbbs from gdb to get a core dump file created upon segfault. Check your /tmp directory or wherever you have your system configured to save core dumps.
you might have to set your ulimit, too... i've had numerous programs segfault and say a core file was written when in fact none was... setting ulimit as needed allowed the core files to be created properly...
And other tweaks, as outlined here: http://wiki.synchro.net/howto:gdb#core_file
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 147:48:06 |
Calls: | 507 |
Calls today: | 1 |
Messages: | 219696 |