Alexandre Oliva <[EMAIL PROTECTED]> writes: > Here's my first cut at trying to tell how well or how bad we perform > in terms of debug info, that can be dropped into the GCC run-time test > infrastructure and used by means of #include in new tests that add > GUALCHK* annotations (or with separate compilation, if some stuff is > moved into a separate header). > > Thoughts, comments, suggestions, tomatoes, eggs? :-)
It's an interesting approach. Have you considered an approach more like Dejagnu's dg support? It would be harder to write tests, but would permit testing debugging info less invasively. int main (int argc, char *argv[]) { int i = argc+1; int j = argc-2; int k = 5; /* { gualchk argc 1 } */ /* { gualchk i 2 } */ /* { gualchk j -1 } */ } Ian