Re: [gdb-7.0 release] 2009-09-02 status and proposed plan

Paul Pluzhnikov
2009-09-15T20:28:42Z

On Mon, Sep 14, 2009 at 10:43 AM, Paul Pluzhnikov
<ppluzhnikov@google.com> wrote:

> And another one :-(
>
> We have a bug report, where doing "break file:line" inserts 13 breakpoints
> with GDB CVS, but only 9 with GDB-6.8.
>
> The problem is that the extra 4 insertions are all in the middle of
> instruction(s), and cause inferior to SIGSEGV if any of these instructions
> is ever executed.
>
> This is happening in a large piece of optimized code, still working on
> reduced test case. Analysis so far:

This was apparetnly a false alarm: both gdb-6.8 and gdb-cvs construct an
identical list of 20 candidates, 4 of which are wrong. And then gdb-6.8
happens to filter out the wrong ones, while gdb-cvs doesn't.

The reason bad candidates are there in the first place is corrupt line
table, due to a bug in gold:
http://sourceware.org/bugzilla/show_bug.cgi?id=10400

I don't believe there is any way to detect and/or work around this in GDB.

Sorry for the noise.
--
Paul Pluzhnikov