Well, unfortunately GDB is no help at all. Can't figure out how to get it to run the mud, without freezing it, etc. Even if it did run the mud, it wouldn't likely be any help in analyzing what's not being done (or is being done wrong). A man file would help, but if it's as confusing as the refcards, it probably wouldn't help at all. Thanks to all who tried. I guess this is just another one of those I'll have to figure out over time.
------------------------------------------- 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Groothuis Sent: Sunday, January 13, 2002 7:28 PM To: Tom Whiting Cc: [email protected] Subject: Re: speaking of progs :) On Sun, Jan 13, 2002 at 07:23:08PM -0600, Tom Whiting wrote: > It's not causing any kind of a dump at all, it's just not > understanding the trigger. The mud's fine, it doesn't crash, the > trigger just doesn't get recognized. That's why you have to run it in GDB, and put breakpoints at the right locations. GDB is not only for things which crash, it's also for realtime stepping through to the code and inspection of variables and memory-space. See http://www.refcards.com for a GDB-reference sheet. Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org [EMAIL PROTECTED] | Interested in MUDs? Visit Fatal Dimensions: ------------------+ ------------------+ http://www.FatalDimensions.org/ -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
