[racket-dev] Bad code day

Some days you just can't win.

First, I found a bug in one of my macros.  So I fired up the macro stepper.

That triggered a bug in the macro stepper's derivation parser.  So I tried
to save a macro stepper debugging file.

That further triggered a bug in the macro stepper's debugging file
generator.  So I added some printouts for manual debugging.

And that caused a segfault.

It's a good thing the segfault successfully created a crash report.  If I
had to start debugging C code, I imagine the next step would be my computer
melting.

Carl Eastlund
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20120314/1490071f/attachment.html>