------- Comment #8 from jonathan dot leffler at gmail dot com 2008-03-11 06:55 ------- CVS tree of v6.8 collected from "cvs -d :pserver:[EMAIL PROTECTED]:/cvs/src co -r gdb_6_8-branch gdb" shows that the current code does indeed include *exact_match = 0; early in the find_line_common() function, so that it would not trigger the warning. The latest release code is 6.7.1 - so the problem occurs in the latest released code, but has been fixed in the current development version.
I will relay this to GDB team (basically to stand them down). It appears that GCC team can close this bug. OK - I've closed it as INVALID; I guess that is the correct resolution from the GCC point of view. Sorry to be a trouble - glad it doesn't involve code changes. Not sure that I'd've deduced the problem without the guidance. -- jonathan dot leffler at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35534