Re: [PATCH] Recognize and skip interpreter_p initialization in selftest.exp

[Daniel Jacobowitz <drow@false.org>]

On Sun, Feb 26, 2006 at 01:35:28PM -0500, Fred Fish wrote:
> With the latest development gcc and latest development gdb,
> selftest.exp fails because the breakpoint at captured_main gets set at
> the interpreter_p initialization, which isn't currently one of the
> recognized patterns.  Apparently optimization has gotten better and
> this code has been moved up the instruction stream:
> 
>   (gdb) br captured_main
>   Breakpoint 1 at 0x807c714: file /src/latest/trunk/src/gdb/gdb/main.c, line 241.
>   (gdb) run
>   Starting program: /links/build/latest/trunk/i686-pc-linux-gnu/gdb/gdb/gdb
>   Breakpoint 1, captured_main (data=0xbfdbb3f4) at /src/latest/trunk/src/gdb/gdb/main.c:241
>   241       interpreter_p = xstrdup (context->interpreter_p);

I'm not sure "better" is the word I'd use - how the heck did that
happen?  Could you please verify a couple of things for me: that we are
reasonably close to the beginning of the function, that the prologue
skipper hasn't gone too far, and that the instruction being executed
has actually got some relationship to line 241.

I've noticed some strange failures in this test recently too, but I
haven't had time to look into them.  It's entirely possible that
nothing's wrong and your patch is fine - I'm just being paranoid for
GCC and/or GDB bugs.


-- 
Daniel Jacobowitz
CodeSourcery