public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13858] `set non-stop 1' triggers some fails in gdb.base/break-interp.exp
Date: Fri, 16 Mar 2012 10:18:00 -0000 [thread overview]
Message-ID: <bug-13858-4717-HCdY3X8MpK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13858-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13858
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-03-16 10:18:06 UTC ---
> If I don't turn on displaced stepping in default, I get no fail in
> gdb.base/break-interp.exp. When I turn on displaced stepping in default (by
> add a line in $build_gdb/gdb/testsuite/site.exp), I get following new fails in
> native gdb on x86 linux.
So "set non-stop 1" isn't really necessary to trigger this, just "set
displaced-stepping on", right? Or are you really running the tests in
non-stop+async mode?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-03-16 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 7:07 [Bug gdb/13858] New: " qiyao at gcc dot gnu.org
2012-03-16 7:08 ` [Bug gdb/13858] " qiyao at gcc dot gnu.org
2012-03-16 10:18 ` palves at redhat dot com [this message]
2012-03-16 10:55 ` qiyao at gcc dot gnu.org
2012-03-16 10:58 ` palves at redhat dot com
2012-03-16 11:12 ` qiyao at gcc dot gnu.org
2012-03-16 11:15 ` palves at redhat dot com
2012-03-16 12:07 ` [Bug gdb/13858] displaced stepping " qiyao at gcc dot gnu.org
2015-04-10 9:12 ` cvs-commit at gcc dot gnu.org
2015-04-10 9:15 ` palves at redhat dot com
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=bug-13858-4717-HCdY3X8MpK@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).