Ayep, exactly what it's passing it as. I didn't notice it until today that it was passing it as that rather extensive #, and like I said, I've seen that on slackware, this runs fine, but on a redhat box, it tends to throw a fit. Knowing nothing (and I mean nothing) about signals though, I'm at a loss here.
------------------------------------------- TJW: Head tech, Dreamless Realms Mud Web: http://drealms.kyndig.com Snippets http://drealms.kyndig.com/snippets Telnet telnet://drealms.kyndig.com:9275 The OLC2 Pages http://olc.kyndig.com ------------------------------------------- -----Original Message----- From: Jason Gauthier [mailto:[EMAIL PROTECTED] Sent: Monday, January 07, 2002 3:38 PM To: 'Tom Whiting'; Jason Gauthier; [email protected] Subject: RE: boggled So the very first call to sig_handler is passing sig as -1074789136? > -----Original Message----- > From: Tom Whiting [mailto:[EMAIL PROTECTED] > Sent: Monday, January 07, 2002 4:40 PM > To: 'Jason Gauthier'; [email protected] > Subject: RE: boggled > > > Heh > That's the point, there's 1100+ lines of just THAT. > However, here's the only thing that's really different (up until the > last few lines of the core which tells me (occasionally) where the > problem can be found. > > #0 0x80698d1 in reboot_shutdown (ch=0x0, reboot=Cannot > access memory at > address 0xbfeff783 > ) at act_wiz2.c:1418 > 1418 { > (gdb) backtrace > #0 0x80698d1 in reboot_shutdown (ch=0x0, reboot=Cannot > access memory at > address 0xbfeff783 > ) at act_wiz2.c:1418 > > And in act_wiz2 : Line 1418 points to > /* one main function called multiple times :) */ > void reboot_shutdown(CHAR_DATA *ch, bool reboot) > ------------------------------------------- > TJW: Head tech, Dreamless Realms Mud > Personal: http://twhiting.kyndig.com > Mud: http://drealms.kyndig.com > Snippets http://drealms.kyndig.com/snippets > Telnet telnet://drealms.kyndig.com:9275 > The OLC2 Pages http://olc.kyndig.com > ------------------------------------------- > > -----Original Message----- > From: Jason Gauthier [mailto:[EMAIL PROTECTED] > Sent: Monday, January 07, 2002 3:20 PM > To: 'Tom Whiting'; [email protected] > Subject: RE: boggled > > Instead of the last of the lines, let's see the first. I'm > specifically > interested in > the very FIRST call to sig_handler() and what 'sig' is. > > My guess is something seg faulted, and then do_auto_shutdown() seg > faulted, > initializing the signal handler, running do_auto_shutdown() which seg > faulted, initializing the signal handler and so on. > > > > -----Original Message----- > > From: Tom Whiting [mailto:[EMAIL PROTECTED] > > Sent: Monday, January 07, 2002 4:15 PM > > To: [email protected] > > Subject: boggled > > > > > > >
