From: | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
Newsgroups: | comp.compilers |
Date: | Sat, 14 Feb 2009 17:43:11 GMT |
Organization: | Institut fuer Computersprachen, Technische Universitaet Wien |
References: | 09-02-021 09-02-025 09-02-031 09-02-038 09-02-048 |
Keywords: | assembler, design, debug |
Posted-Date: | 14 Feb 2009 16:51:17 EST |
Marco van de Voort <marcov@stack.nl> writes:
>(to all the people that might have tried C as backend):
>
>How do you insert debug metadata on the HLL level into your binary in such
>setup ? It seems to me your debuginfo will contain C linenumbers, typedata
>etc.
For line numbers the #line directive should also affect the debugging
info, no?
Concerning data, you would have to teach the debuggers a lot about
your source language even if you can give it information about
source-level data and variable, right?
> IOW, how do you debug in your HLL this way?
Typically with print-statement debugging. I also found backtraces
quite useful, whereas gdb-style debuggers are often a way to waste a
lot of time (let's step a little further, maybe the bug will show up
here); and when I find them useful, I typically want to see stuff at a
low level (typically machine-level), anyway, but that may just be due
to the things I program.
- anton
--
M. Anton Ertl
anton@mips.complang.tuwien.ac.at
http://www.complang.tuwien.ac.at/anton/
Return to the
comp.compilers page.
Search the
comp.compilers archives again.