This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Sporadic failures of selftest tests
- From: Pedro Alves <palves at redhat dot com>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>, gdb-patches at sourceware dot org
- Date: Tue, 17 Oct 2017 15:34:17 +0100
- Subject: Re: Sporadic failures of selftest tests
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=palves at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1933037E7B
- References: <20171017140032.2D8AAD807C2@oc3748833570.ibm.com> <7e8c90cf-c12b-0095-16e5-3dcae94aff6f@redhat.com>
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