DM,
v3.16c is sefaulting on me. I'm just recompiled without the RELEASE=1 to get the debug.exe. What info do you need?
syslog error is : segfault at 6262732f ip b6d07733 sp b12dcfa0 error 4 in libc-2.21.so[b6cc2000+1a1000]
A backtrace might be helpful. Here are instructions on how to get one: http://wiki.synchro.net/howto:gdb
Re: v3.16c sefaulting
By: Digital Man to echto on Sat Jan 23 2016 01:32:18
Thanks. I can't even access the message bases now without sbbs segfaulting. I'll take a look at you how-to. Here is a paste bin from gbd.
http://pastebin.com/Tw2L3ZmQ
A backtrace might be helpful. Here are instructions on how to get
one: http://wiki.synchro.net/howto:gdb
OK, even after making the changes to sysctl, sbbs is not dumping a
core. ulimit is set to unlimited. I did get a backtrace in gdb, but according to your wiki you only want the output "if (and only if) the
last line..." has a certain look. I posted a 'bt full' to pastbin earlier.
Anyway, I started up v3.17a and I am able to access the message bases without a segfault. The only issue I have noticed with v3.17a is the
ssh service does not start.
Do you see the problem? At the very least, you will eventually run out of space for the call stack, but you're like to have other weird side effects too.
Re: v3.16c sefaulting
By: Digital Man to echto on Sat Jan 23 2016 15:43:46
Do you see the problem? At the very least, you will eventually run out of space for the call stack, but you're like to have other weird side effects too.
Ah.. ok. Yeah, I'll have to go through things and see what I did. It's been a couple of years since I messed with this. Only recently has life started settling down (google "Abigail Mounce")
Oh wow, sad. Glad she survived and the community has helped with her recovery! Rock on,
OK, even after making the changes to sysctl, sbbs is not dumping a core. ulimit is set to unlimited. I did get a backtrace in gdb, but according to your wiki you only want the output "if (and only if) the last
line..." has a certain look. I posted a 'bt full' to pastbin earlier.
Welcome to my world. Well, not on the same version (I'm still on 3.16b), but I can't get the damn thing to leave a stack trace for me for the life of me. I've got everything else leaving traces that core dumps on this OBSD machine except for that. It's enough to drive a person batty.
Oh wow, sad. Glad she survived and the community has helped with her
recovery! Rock on,
I am too! Thanks!
Programs that call setuid() often require special magic to get cores from since they may have some secret root stuff in the image.
On FreeBSD, you need to do a ``sysctl kern.sugid_coredump=1'' to get them to dump. I have that in my /etc/sysctl.conf.
Quite likely there's something similar for OpenBSD and Linux too.
recovery! Rock on,
I am too! Thanks!
Yes, sad story with happy ending, or at least a good ending.
they ask me if i want a happy ending at the massage parlor but i tell them i'm just there to get my back fixed up.
Re: v3.16c sefaulting
By: Mro to Joe Delahaye on Mon Jan 25 2016 17:27:45
they ask me if i want a happy ending at the massage parlor but i tell them i'm just there to get my back fixed up.
You should ask for a Wax Job <G>
You should ask for a Wax Job <G>
you mean a brazillian? i dont know if they have enough wax for that.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 15:55:00 |
| Calls: | 15,171 |
| Calls today: | 4 |
| Files: | 19,857 |
| D/L today: |
84 files (7,771K bytes) |
| Messages: | 1,691,824 |