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
I ran it several times in a console window and got a segmentation fault at various stages.
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.
The latest CVS sources compile and run just fine on the Windows 10 "linux":
uname --all
Linux RLQ 4.4.0-17134-Microsoft #345-Microsoft Wed Sep 19 17:47:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
Now on to BINKIT.
I have a node configured in sbbsecho as such:
[node:314:314/0@piNet]
Name = NecroBBS PiNet Feed
Comment = piNET HQ
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = SECRET
SessionPwd = SECRET
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = true
Notify = false
Keys = P
Status = Normal
LocalAddress = 314:314/45
GroupHub =
BinkpHost = necrobbs.strangled.net
BinkpPort = 24556
BinkpPoll = true
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress = 314:314/45
I also have this:
[node:314:ALL]
Name =
Comment =
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd = yaesu
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys = P
Status = Normal
Route = 314:314/0
LocalAddress = 314:314/45
GroupHub =
BinkpHost =
BinkpPort = 24556
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress = 314:314/45
However, when BINKIT calls out, it tries to use "example.com".
[callout failure: 314:314/0]
host = f0.n314.z314.example.com
port = 24554
connect_error = 0
localtime = Feb 16 2019 20:51:57
From where can BINKIT possibly be getting "example.com"? The above
node is also not the only one for which BINKIT tries to contact "example.com".
Another BINKIT issue I noticed is that it seems to call itself:
[callout success: 9:91/2@survnet]
oper = Ray Quinn
AKAs = 1:214/22@fidonet,1:214/0@fidonet,1:214/1@fidonet,9:91/2@survn et,24:160/1@sportn et,24:160/0@sportnet,24:160/22@sportn$
caps = 115200,TCP,BINKP
vers = BinkIT/2.17,JSBinkP/1.114,sbbs3.17a/Linux
host = bbs.quinnnet.org
port = 24554
info.sys = US 99 BBS
info.loc = Visalia, CA
info.time = Sun Feb 17 2019 09:30:59 GMT-0800 (PST)
localtime = Feb 17 2019 09:31:04
This node is opviously not configured in sbbsecho.ini as it is a system address.
Any ideas?
I am going to address the segmentation fault first.
Now on to BINKIT.
I have a node configured in sbbsecho as such:
[node:314:314/0@piNet]
I also have this:
[node:314:ALL]
Name =
Comment =
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd = yaesu
However, when BINKIT calls out, it tries to use "example.com".
[callout failure: 314:314/0]
host = f0.n314.z314.example.com
port = 24554
connect_error = 0
localtime = Feb 16 2019 20:51:57
From where can BINKIT possibly be getting "example.com"? The above
node is also not the only one for which BINKIT tries to contact "example.com".
sbbs@bbs:/sbbs/exec$ grep example.com ../data/*
../data/binkstats.ini: host = f756.n322.z1.example.com ../data/binkstats.ini: host = f1.n104.z900.example.com ../data/binkstats.ini: host = f0.n314.z314.example.com
Another BINKIT issue I noticed is that it seems to call itself:
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...
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.
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: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 28 |
Nodes: | 8 (0 / 8) |
Uptime: | 191:18:15 |
Calls: | 2,006 |
Calls today: | 3 |
Files: | 11,114 |
Messages: | 942,287 |