Well if you're not monitoring the gdb session, the first time the mud crashes or hits a breakpoint of any kind, gdb will trap it there, so from the standpoint of being logged into the mud, it will appear to just hang, when in fact, gdb is just waiting for you to examine what you want to examine and type continue to let it keep running the program... if you're having the problem right after you attach gdb to it, it's because attaching it freezes the mud for a while so you can set watches and breakpoints, and you need to 'continue' it to let the program keep running...
Richard Lindsey Network Administrator INTERA, Inc. 9111A Research Blvd. Austin, TX 78758 (512) 425-2006 [EMAIL PROTECTED] -----Original Message----- From: Valnir [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 1:10 PM To: [email protected] Subject: Re: Segmentation Fault I have a question (regarding gdb). I have had issues trying to leave the mud running in gdb. I always end up with the mud in a "hung" state when I try this. What am I doing wrong? -Valnir ----- Original Message ----- From: "Richard Lindsey" <[EMAIL PROTECTED]> To: "Matthew Martin" <[EMAIL PROTECTED]>; <[email protected]> Sent: Monday, May 10, 2004 2:03 PM Subject: RE: Segmentation Fault I'd suggest leaving the mud running in gdb... when it segfaults, gdb should catch it and show you where, then you can check the info on some of the variables in use and see why it's crashing... if you don't know how to attach gdb to the mud when it's already running just go to your shell, ps -ux, get the mud's pid, and type gdb ./src <pid> continue and just let it run it's natural course... Richard Lindsey -----Original Message----- From: Matthew Martin [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 10:04 AM To: [email protected] Subject: Segmentation Fault I keep getting this message in my shell. No crashes, no core dumps, just a Segmentation fault, mud kills, then restarts. I started logging all of the processes running in update.c to see where the Seg fault was coming from, but after perusing the logs, it doesn't seem to be occuring in a specific location...Sometimes it kills on mob_update, sometimes on obj_update, but it's not reproducable, at least, not that I've been able to find. Any of you guys have an idea for me? _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.com/go/onm00200415ave/direct/01/ -- 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 -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
