On Tuesday, February 03, 1998 6:15 PM, George [SMTP:greerga@CIRCLEMUD.ORG]
wrote:
> >> >Stack dump:
> >> >00000000 815a49b4 004014c4 00000000 00000000 815a49b4 005e0000
815a49b4
> >> >
> >> >005e0000 00000019 34d783d4 00000030 006efdf8 00401407 00000fa0
00000000
> >> >
> >>
> >> Don't suppose you could decode that?
> >Here we go, the text reads: zero-zero-zero-zero-zero-zero-zero-zero
> >eight-one-five-a-four-nine-b-four... (: In English? OK...:
>
> Yeah, thanks.
>
> Those numbers could be any function in the MUD (or not even valid)
> depending on alignment, code generation, what he has, or even the
> alignment
> of the moon and stars. So a stack trace is useless without the names. The
> NULL's look a bit odd though.
>
> Look in the code at that address and see what function is there.
> (Or try to have VC do it for you somehow.)
>
Visual C?
1) Click Debug when the mud crashes.
2) Select view/debug/call stack (or use ALT-7)
3) Double click on each line of the call stack to view the code in the file
where that line exists.
4) Poke around and look at variables (Select the variable, press shift-F9 or
debug/quick watch)
5) Set a breakpoint right before where you think you have the problem (right
click/insert breakpoint) then restart the program and reproduce the original
bug. Then look at the variables and step through until you figure out where
you screwed up. :-)
95/NT doesn't produce a 'core file' AFAIK. You have to be there to catch the
error, and the 'debugging' info produced is pretty much
useless to a hobbyist :-)
--Mallory
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST