Sporadic failures of selftest tests
Pedro Alves
palves@redhat.com
Tue Oct 17 14:34:00 GMT 2017
On 10/17/2017 03:24 PM, Pedro Alves wrote:
> Now the question should be why did GDB stop there, when breakpoint 1
> was supposedly set on captured_command_loop ?
>
> > (gdb) break captured_command_loop
> > Breakpoint 1 at 0x7117b0: file ../../binutils-gdb/gdb/main.c, line 324.
> > (gdb) PASS: gdb.gdb/complaints.exp: breakpoint in captured_command_loop
> ...
> > (gdb)
> > Breakpoint 1, captured_main (data=0x7fffffffd2e0) at ../../binutils-gdb/gdb/main.c:1147
> > 1147 captured_command_loop ();
>
> That seems to be the root of the problem.
>
> I wonder whether that's somehow related to the other Power regression
> Simon reported:
> https://sourceware.org/ml/gdb-patches/2017-10/msg00444.html
>
> I haven't managed to investigate that one.
>
> Does it reproduce easily for you? If so, I'd suggest a git bisect to
> find the culprit.
Wait, is your build of GDB an optimized build? Maybe the compiler
managed to inline captured_command_loop for you? Currnetly, when
GDB stops for an inline breakpoint, it stops at the stack caller,
which would explain this.
Thanks,
Pedro Alves
More information about the Gdb-patches
mailing list