Related articles |
---|
book on internals of debugger? ajain@ca.merl.com (Anurag Jain) (1993-11-20) |
Re: book on internals of debugger? lacey@zamboni.sps.mot.com (1993-11-22) |
Re: book on internals of debugger? norman@flash.bellcore.com (1993-11-22) |
Re: book on internals of debugger? mav@gaia.cc.gatech.edu (1993-11-22) |
Re: book on internals of debugger? a_tucker@paul.spu.edu (Andrew Tucker) (1993-11-22) |
Re: book on internals of debugger? thutt@clark.net (1993-11-23) |
Re: book on internals of debugger? iwm@doc.ic.ac.uk (1993-11-23) |
[1 later articles] |
Newsgroups: | comp.compilers |
From: | Anurag Jain <ajain@ca.merl.com> |
Keywords: | debug, question, comment |
Organization: | Mitsubishi Electric Research Labs |
Date: | Sat, 20 Nov 1993 02:18:32 GMT |
Hello,
Could anyone please recommand me a book/literature/course on internals
of debugger. For example, when user sets a break- point in a debugger,
s/he may say "stop at 375 in display.c". Then how does debugger map
source code line 375 to the object file (line) compiled with -g option?
What information does debugger need? How does it make a use of the
debugging information? In general, what steps does debugger take to
perform its operations?
Any help will be greatly appreciated.
Anurag Jain (ajain@ca.merl.com)
PS: Regardless of performance, algorithms that a debugger uses to perform
its major operations (like setting a break point) will also be helpful.
[Are these collected in a book anywhere, or are they all just folklore? -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.