Platform: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
An amd x64 PC running Raspbian X86_64 PC. Synchronet compiles without error using make RELEASE=1 DOSEMU=1 JSINCLUDE=/usr/include/js JSLIB=mozjs185
When I run sudo /sbbs/exec/sbbs I get 'Segmentation Fault'
I believe it is
because it is because it is amd x64 ...
is there a way for the build to
compile as 32bit? ie gcc -m32 ... and if yes where does one set that flag?
Re: Linux Build woes
By: Mortifis to All on Mon Oct 22 2018 09:51 am
Platform: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
An amd x64 PC running Raspbian X86_64 PC. Synchronet compiles without error using make RELEASE=1 DOSEMU=1 JSINCLUDE=/usr/include/js JSLIB=mozjs185
When I run sudo /sbbs/exec/sbbs I get 'Segmentation Fault'
Can you capture a provide a backtrace? http://wiki.synchro.net/howto:gdb
I believe it is
because it is because it is amd x64 ...
Why do you believe that? Is there some known problem with native compiled apps on that platform?
is there a way for the build to
compile as 32bit? ie gcc -m32 ... and if yes where does one set that flag?
Certainly there is a way, but we don't have cross-compilation built-into the Synchronet build system - so it's not trivial to do. The best way to build a 32-bit version of sbbs is to build it in a 32-bit environment. But I'm skeptical that that is the issue here.
digital man
Re: Linux Build woes
By: Mortifis to All on Mon Oct 22 2018 09:51 am
Platform: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
An amd x64 PC running Raspbian X86_64 PC. Synchronet compiles without error using make RELEASE=1 DOSEMU=1 JSINCLUDE=/usr/include/js JSLIB=mozjs185
When I run sudo /sbbs/exec/sbbs I get 'Segmentation Fault'
Can you capture a provide a backtrace? http://wiki.synchro.net/howto:gdb
output from sudo gdb /sbbs/exec/sbbs
[Threads: 8 Sockets: 4 Clients: 0 Served: 0 Errors: 0] (?=Help):
Thread 8 "sbbs/webServer" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xf3dffb40 (LWP 22256)]
0xf7e3fc86 in aes_encrypt_key128 ()
from /sbbs/src/sbbs3/gcc.linux.x64.lib.release/libsbbs.so
Re: Re: Linux Build woes
By: Mortifis to Digital Man on Mon Oct 22 2018 07:30 pm
[Threads: 8 Sockets: 4 Clients: 0 Served: 0 Errors: 0] (?=Help): Thread 8 "sbbs/webServer" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xf3dffb40 (LWP 22256)]
0xf7e3fc86 in aes_encrypt_key128 ()
from /sbbs/src/sbbs3/gcc.linux.x64.lib.release/libsbbs.so
Okay, that crash is in cryptlib, a 3rd party crypto library which we use for SSH/SSL/TLS and which gets patched before we build and link the library. Anyway, you can probably avoid that particular crash point by disabling SSL/TLS in the web server by remove ALLOW_TLS from the [web] Options in your ctrl/sbbs.ini file. It may crash at some other point in cryptlib and you may need to disable TLS support for services or the mail server as well. See what happens after disabling it in the web server first.
digital man
Okay, that crash is in cryptlib, a 3rd party crypto library which we use for SSH/SSL/TLS and which gets patched before we build and link the library. Anyway, you can probably avoid that particular crash point by disabling SSL/TLS in the web server by remove ALLOW_TLS from the [web] Options in your ctrl/sbbs.ini file. It may crash at some other point in cryptlib and you may need to disable TLS support for services or the mail server as well. See what happens after disabling it in the web server first.
That worked, Thank you.
Re: Re: Linux Build woes
By: Mortifis to Digital Man on Tue Oct 23 2018 09:05 am
Okay, that crash is in cryptlib, a 3rd party crypto library which we use for SSH/SSL/TLS and which gets patched before we build and link the library. Anyway, you can probably avoid that particular crash point by disabling SSL/TLS in the web server by remove ALLOW_TLS from the [web] Options in your ctrl/sbbs.ini file. It may crash at some other point in cryptlib and you may need to disable TLS support for services or the mail server as well. See what happens after disabling it in the web server first.
That worked, Thank you.
Okay. That's interesting and kind of scary too. If your distro has a cryptlib(-dev) package, it might be better to install that package and link with that library instead - but if you don't care about HTTPS, then you might be fine with the way things are now.
digital man
Re: Re: Linux Build woes
By: Mortifis to Digital Man on Tue Oct 23 2018 09:05 am
Okay, that crash is in cryptlib, a 3rd party crypto library which we use for SSH/SSL/TLS and which gets patched before we build and link the library. Anyway, you can probably avoid that particular crash point by disabling SSL/TLS in the web server by remove ALLOW_TLS from the [web] Options in your ctrl/sbbs.ini file. It may crash at some other point in cryptlib and you may need to disable TLS support for services or the mail server as well. See what happens after disabling it in the web server first.
That worked, Thank you.
Okay. That's interesting and kind of scary too. If your distro has a cryptlib(-dev) package, it might be better to install that package and link with that library instead - but if you don't care about HTTPS, then you might be fine with the way things are now.
digital man
Noticed now that sbbs crashes often, it runs as a service so it does restart itself, I ran cat /var/log/syslog 2>&1 | grep segfault | tee /sbbs/segfault.log which now shows dozens of entries like:
Oct 24 06:27:29 pos-x64-pc kernel: [4539125.848688] sbbs/pop3[9478]: segfault at f9fda829 ip 00000000f763ac86 sp 00000000eeff9960 error 6 in libsbbs.so[f73d0000+3a0000]
Any ideas, other than not trying to use that POS PC :-P
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 189:52:19 |
| Calls: | 2,004 |
| Calls today: | 1 |
| Files: | 11,114 |
| Messages: | 942,281 |