From: Pedro Alves <palves@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: Sporadic failures of selftest tests
Date: Tue, 17 Oct 2017 14:40:00 -0000 [thread overview]
Message-ID: <9c64bb67-3917-92b7-dae5-3a14c4879d6c@redhat.com> (raw)
In-Reply-To: <39dde79f-2540-6718-8fab-e65b159fdf9f@redhat.com>
On 10/17/2017 03:34 PM, Pedro Alves wrote:
> 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.
Yup, I can reproduce this with:
$ rm -f main.o && make CXXFLAGS="-g3 -O2"
$ make check TESTS="*/complaints.exp"
[...]
Running src/gdb/testsuite/gdb.gdb/complaints.exp ...
FAIL: gdb.gdb/complaints.exp: run until breakpoint at captured_command_loop
WARNING: Couldn't test self
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-10-17 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:00 Ulrich Weigand
2017-10-17 14:25 ` Pedro Alves
2017-10-17 14:34 ` Pedro Alves
2017-10-17 14:40 ` Pedro Alves [this message]
2017-10-17 14:55 ` Pedro Alves
2017-10-17 15:48 ` Ulrich Weigand
2017-10-17 15:54 ` Pedro Alves
2017-10-17 16:12 ` Pedro Alves
2017-10-20 12:51 ` Ulrich Weigand
2017-10-20 14:32 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c64bb67-3917-92b7-dae5-3a14c4879d6c@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).