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
>
>
