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/14135] New: Fails in gdb.python/py-finish-breakpoint.exp when `set target-async on'.
Date: Wed, 23 May 2012 08:02:00 -0000 [thread overview]
Message-ID: <bug-14135-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14135
Bug #: 14135
Summary: Fails in gdb.python/py-finish-breakpoint.exp when `set
target-async on'.
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: qiyao@gcc.gnu.org
Classification: Unclassified
These fails are mentioned here
http://sourceware.org/ml/gdb-patches/2012-05/msg00290.html. Track them in this
PR.
Run test suite with async mode, then we can see following fails.
FAIL: gdb.python/py-finish-breakpoint.exp: check MyFinishBreakpoint hit (GDB
internal error)
FAIL: gdb.python/py-finish-breakpoint.exp: check stopped location
FAIL: gdb.python/py-finish-breakpoint.exp: stop in condition function
FAIL: gdb.python/py-finish-breakpoint.exp: stop at conditional breakpoint
Noe that this test case fails (in async mode) when it was introduced by this
commit 7c56fb07bde331d79eb73ece26b8fc960aa13eb2.
--
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 reply other threads:[~2012-05-23 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 8:02 qiyao at gcc dot gnu.org [this message]
2012-05-23 8:07 ` [Bug gdb/14135] " qiyao at gcc dot gnu.org
2012-05-23 10:28 ` kevin.pouget at gmail dot com
2012-05-23 10:40 ` qiyao at gcc dot gnu.org
2012-05-23 10:58 ` kevin.pouget at gmail dot com
2012-05-23 11:12 ` qiyao at gcc dot gnu.org
2012-06-08 13:09 ` qiyao at gcc dot gnu.org
2013-07-31 17:45 ` tromey at redhat dot com
2014-03-20 18:22 ` cvs-commit at gcc dot gnu.org
2014-03-20 18:36 ` 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-14135-4717@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).