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.
|
