|need ideas on how to debug code generator firstname.lastname@example.org (Ram Bhamidipaty) (2008-02-24)|
|Re: need ideas on how to debug code generator email@example.com (Thomas Have) (2008-02-25)|
|Re: need ideas on how to debug code generator firstname.lastname@example.org (Nils) (2008-02-26)|
|Re: need ideas on how to debug code generator email@example.com (Bartc) (2008-02-27)|
|Re: need ideas on how to debug code generator firstname.lastname@example.org (Joel Yliluoma) (2008-02-28)|
|From:||Thomas Have <email@example.com>|
|Date:||Mon, 25 Feb 2008 17:59:42 +0100|
|Posted-Date:||25 Feb 2008 19:38:30 EST|
Ram Bhamidipaty wrote:
> The test case in question generates a code sequence of about 400 bytes. It
> fails by seg faulting, unfortunately gdb is unable to print out a
> useful stack trace.
On the windows platform, perhaps windbg (google debugging tools for
windows) could be of use. Especially, I think that adplus in hang mode
could be helpfull. (Windbg has a rather steep learning curve
though. See below also :)).
> What are some techniques that people have used for debugging code
Unfortunately I haven't had the pleasure of debugging generated x86
code (but other generators).
Thomas *thomash* Have.
Return to the
Search the comp.compilers archives again.