On Thu, 29 Feb 1996, MUD wrote: > > --- SNIP START --- > > Core was generated by `bin/ConMUD.exe 5000'. > > Program terminated with signal 11, Segmentation fault. > > #0 0xdf662de4 in ?? () > > (gdb) back > > #0 0xdf662de4 in ?? () > > Cannot access memory at address 0xdfffc614. > > (gdb) > > --- SNIP END - > > > > Can anyone tell me what this means ? > > Has anyone experienced anything similar, if so, how did you remove the 'bug= > > ' ? > > > > Any additional response is welcome. > > I've been having similar cases but never have I experienced that it > ruins the name of the function that caused the crash or something. > gdb usually tells you that it cannot access memory likewise. > Well, are the segfaults caused when trying to change the area out of > bounds or just when already changed it? > > What I have experienced is when you get the message like 'cannot access > memory' you should run circle under the gdb. That insures that you > are able to see backtrace at least. hehe Yes, well, the problem is that I can't myself create this error, my mud crashes after several hours, and somethimes it takes a day wich makes it impossible for me to stay in gdb (would halt the mud if I wasnt present when it crashed), so I only have the option to load up the corefile (wich then again only gives this limited information). Anyway, do you have any idea as to how to reproduce an error like this ? Regards, Con. d. -- *************************************************************************** * * Visit my homepage: * * Rasmus Rønlev DOEK'94 * http://www.econ.cbs.dk/people/raro94ab * * Student instructor * Visit my Multi User Dungeon (MUD): * * * ns3.ptd.net 5000 or 198.80.46.3 5000 * *************************************************************************** * * * Student, B.Sc in Computer Science and Business Administration * * * ***************************************************************************
This archive was generated by hypermail 2b30 : 12/07/00 PST