public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <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 11:12:00 -0000 [thread overview]
Message-ID: <bug-13858-4717-hhR94Dton8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13858-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13858
--- Comment #4 from Yao Qi <qiyao at gcc dot gnu.org> 2012-03-16 11:12:20 UTC ---
(In reply to comment #3)
> > set GDBFLAGS "-ex \"set non-stop 1\""
>
> That's not proper non-stop, you need to enable async as well.
>
I got the same fails as below when run non-stop + async.
> But, what happens with just
>
> set GDBFLAGS "-ex \"set displaced-stepping on\""
>
> afterall?
This is what I got,
Running ../../../gdb/gdb/testsuite/gdb.base/break-interp.exp ...
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: BINprelinkNOdebugNOpieNO:
symbol-less: reach-_dl_debug_state: reach
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: BINprelinkNOdebugNOpieNO:
symbol-less: entry point reached
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: BINprelinkNOdebugNOpieYES:
symbol-less: reach-_dl_debug_state: reach
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: BINprelinkNOdebugNOpieYES:
symbol-less: entry point reached
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkNOdebugNOpieNO:
symbol-less: reach-_dl_debug_state: reach
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkNOdebugNOpieNO:
symbol-less: entry point reached
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkNOdebugNOpieYES:
symbol-less: reach-_dl_debug_state: reach
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkNOdebugNOpieYES:
symbol-less: entry point reached
=== gdb Summary ===
# of expected passes 659
# of unexpected failures 8
# of expected failures 20
/home/yao/SourceCode/gnu/gdb/git.new/build-x86/gdb/testsuite/../../gdb/gdb
version 7.4.50.20120306-cvs -nw -nx -data-directory
/home/yao/SourceCode/gnu/gdb/git.new/build-x86/gdb/testsuite/../data-directory
-ex "set displaced-stepping on"
--
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 11:12 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
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 [this message]
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-hhR94Dton8@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).