Hi,
First off, this message is written in sheer desperation *g* Seccondly I'm
sorry to those who don't like these type of posts, but I have no idea
where else I should direct it. If someone knows of a newsgroup that will
answer questions pertaining debugging with gdb, I'd highly appreciate some
info about it.
On I go :)
The mud I code on runs on Linux, and beeing that this system is in a
constant development I kinda suspect the reason of the wierd messages I
get to be because of this. I'm running the mud with a somewhat hacked up
version of the gdb-script at the circlemud site, and this is the info I
get from gdb when the mud crashes:
Program received signal SIGSEGV, Segmentation fault.
0x4003c40d in __libc_free ()
(gdb) #0 0x4003c40d in __libc_free ()
#1 0xbfffc538 in ?? ()
Not exactly very easy to debug this :P What I don't understand is the :
' #1 0xbfffc538 in ?? () ' part. Why does GDB show this ?? () stuff ? It
happens on a lot of occasions, so I was wondering if it's something that
other people have a good explanation for, or if it's perhaps something in
the linux libraries that needs to be reconfigured or something..
I was thinking in the lines of compiling the libc libraries oneself if
that is possible with something similar to the -g option when compiling
the mud.. Do I need to do something like that, or does GDB know how to
keep track of this itself ? I wish I was running a mud on SunOS *g* there
I allways got some output I could understang <evil grin>
Well, hope someone can help me, or point me in the right direction to
resolve this.
Regards,
Con
d.
--
Rasmus Rønlev DOEK'94 WWW: http://www.econ.cbs.dk/people/raro94ab
Student instructor MUD: exiled.mud.circlemud.org 5000
199.199.16.100 5000
Student, B.Sc in Computer Science and Business Administration.
+-----------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://cspo.queensu.ca/~fletcher/Circle/list_faq.html |
+-----------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/18/00 PST