Re: need ideas on how to debug code generator

Thomas Have <thomas@povtal.org>
Mon, 25 Feb 2008 17:59:42 +0100

          From comp.compilers
Related articles
need ideas on how to debug code generator rambham@gmail.com (Ram Bhamidipaty) (2008-02-24)
Re: need ideas on how to debug code generator thomas@povtal.org (Thomas Have) (2008-02-25)
Re: need ideas on how to debug code generator n.pipenbrinck@cubic.org (Nils) (2008-02-26)
Re: need ideas on how to debug code generator bc@freeuk.com (Bartc) (2008-02-27)
Re: need ideas on how to debug code generator bisqwit@iki.fi (Joel Yliluoma) (2008-02-28)
| List of all articles for this month |
From: Thomas Have <thomas@povtal.org>
Newsgroups: comp.compilers
Date: Mon, 25 Feb 2008 17:59:42 +0100
Organization: TDC Totalloesninger
References: 08-02-079
Keywords: debug
Posted-Date: 25 Feb 2008 19:38:30 EST

Hello,


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
> generators?


Unfortunately I haven't had the pleasure of debugging generated x86
code (but other generators).


Kind regards,


Thomas *thomash* Have.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.