Thanks Aryeh & Chuck. Well, I am trying to solve issues related to GDB. Like, gdb prints wrong values of few parameteres eg "this" pointer, when we give "backtrace" or "x/10x $ebp" command in core of our company product. I think it reads wrong value from symbol table or stack frame. So i am trying to put a break point and see what exactly gdb reads for that perticuler frame when it shows a wrong data. But dont know where exactly it reads data from the symbol table or stack frame. If you have a specific idea regarding this pls give some more info. Regards.
----- Original Message ---- From: Chuck Swiger <[EMAIL PROTECTED]> To: Arun Paneri <[EMAIL PROTECTED]> Cc: FreeBSD User <[EMAIL PROTECTED]>; firstname.lastname@example.org Sent: Wednesday, January 16, 2008 2:56:36 PM Subject: Re: Pls help: regarding gdb internals On Jan 16, 2008, at 10:58 AM, Arun Paneri wrote: > Can anyone write few lines about how does gdb internally works. I > went to "Gdb internals guide" but couldn't find much information > specifically which i am looking for. I'm not familiar with the document you mentioned, but the canonical documentation for GDB is available via "info gdb". > I want information like when we give command "$gdb test.exe" then > how internaly it works. Does it start reading symbols and start > making symbol table with this command? Binary objects such as executable programs, shared libraries, etc contain symbol tables; GDB does a quick load of this symbol data to identify all of the sources of symbols for the program, and then will look up the details when needed. > Does it start creating stack frames as we give command "run" or > before even that? The program being debugged does not exist as a process until you run it, so there isn't an address space or stack until then. When the target program is run, it creates it's own stack frames according to the local architecture's machine calling conventions. > I am basically interested to know about creation of frames and how > does gdb read them back when we give "backtrace" command? Well, the calling conventions are different for every particular CPU architecture; but if you want to see the code that GDB uses, start with: /usr/src/contrib/gdb/gdb/frame-base.c /usr/src/contrib/gdb/gdb/frame-base.h /usr/src/contrib/gdb/gdb/frame-unwind.c /usr/src/contrib/gdb/gdb/frame-unwind.h /usr/src/contrib/gdb/gdb/frame.c /usr/src/contrib/gdb/gdb/frame.h ...but I suspect that something like these two articles are closer to what you are looking for: http://en.wikipedia.org/wiki/Calling_convention http://en.wikipedia.org/wiki/X86_calling_conventions -- -Chuck ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"