bare with me here, but I think I may have an answer.. maybe.
I am not sure about your mud in particular but in mine
(built in Windows with MSVC++ and runs and compiles in Linux AND Windows)
I have the option of compiling a "debug" version or a release version..
you might be using a command line in your compile that removes your debug
info..
(makes for a smaller executable).. not sure though, just a thought.
----- Original Message -----
From: "Davion Kalhen" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, November 18, 2004 1:31 PM
Subject: Re: gdb doesn't have a stack?
Try running the MUD under GDB, that might help things alittle. If its
running, 'gdb attach <pid>'. To boot it up 'gdb path/to/executable',
then just 'run <port>', then crash it. If there is still no stack,
then, well, set up logs in the code to see where its crashing
Davion
On Wed, 17 Nov 2004 17:01:49 -0500, Rick St Jean <[EMAIL PROTECTED]>
wrote:
When my mud crashes it leaves me a nice core.### file. which was awesome in
the past. I used to be able to specify the file .. then build the
tables. I cannot
do that any longer, each time I try ... I get no stack. how can I get my
debug info
back?
Rick
--
ROM mailing list
[email protected]
http://www.rom.org/cgi-bin/mailman/listinfo/rom
--
ROM mailing list
[email protected]
http://www.rom.org/cgi-bin/mailman/listinfo/rom
