>>>>> "Michael" == Michael T <rasel...@hotmail.com> writes:
Michael> I was wondering if it is possible to improve the debugging Michael> information generated by gcc when resolving C macros? It could be done, but nobody has tried. Michael> I wonder whether this couldn't be done by the gcc preprocessor? Michael> Or does standards compliance forbid this? A DWARF extension might be needed, but that is not a big deal. The bulk of the work will be defining exactly what you want in various cases, and then of course the implementation in GCC. It isn't clear to me that you always want to emit this information. E.g., there are some hairy macros in libc that, presumably, only libc developers would ever want to step through. Look for a 6 part series from Dodji Seketeli in December 2010 for some work that would be a good starting point for this. The first message is titled "[PATCH 0/6] Tracking locations of tokens resulting from macro expansion". This series changes GCC to more accurately track source locations through macro expansion. Tom
