|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:||Ram Bhamidipaty <email@example.com>|
|Date:||Sun, 24 Feb 2008 21:47:50 -0800|
|Keywords:||code, errors, question|
|Posted-Date:||25 Feb 2008 09:56:45 EST|
I have a small code generator - for 32 bit x86 machines, unfortunately it
has some bugs :-(. My problem is that the generated code fails
"once in a while" sometimes it can go for 20-40 iterations before failing.
I have a collection of test cases where I verify the correctness of
various simple constructs -- things like load, store, add, sub, etc.
Those all pass.
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.
What are some techniques that people have used for debugging code
Return to the
Search the comp.compilers archives again.