Re: Non-stop Multi-Threaded Debugging in GDB - GCC summit paper published

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:

Mark> Also published is Alexandre Oliva's paper on:
Mark> A Plan to Fix Local Variable Debug Information in GCC
Mark> http://ols.fedoraproject.org/GCC/Reprints-2008/oliva-reprint.pdf

FWIW there's a competing proposal:

Improving the precision of GCC's debug information, by Michael Matz:
http://ols.fedoraproject.org/GCC/Reprints-2008/matz-reprint.pdf

... and Andrew MacLeod said recently on the GCC list that he's looking
at a way to quantify GCC's debug info output quality.


Note that one of these two variable tracking projects is necessary,
but not sufficient.  There are plenty of other missing debuginfo bits
which are unrelated to these; here's a query showing some c++ ones
(there may be more, I didn't look exhaustively):

http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=c%2B%2B&product=gcc&component=debug&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=


Tom