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] Fails in gdb.python/py-finish-breakpoint.exp when `set target-async on'.
Date: Wed, 23 May 2012 11:12:00 -0000	[thread overview]
Message-ID: <bug-14135-4717-O6oMWH8rRH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14135-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14135

--- Comment #4 from Yao Qi <qiyao at gcc dot gnu.org> 2012-05-23 11:12:26 UTC ---
(In reply to comment #3)
> 
> I'm not sure to understand your position here: would you like me to change
> appropriately "gdb.execute ("where 1")" and fix the testsuite failure, or will
> you guys try to fix the underlying problem ?

I am not sure on this either :)  It is good if we can fix the underlying
problem, but don't know how much work it needs.  At the same time, I'd like to
remove "gdb.execute ("where 1")" from test case.  I am not familiar with
gdb/python, but the `stop' method is similar to breakpoint condition, and I
feel it is not right to put gdb.execute (which is similar to breakpoint action)
to it.

Anyway, I'll post a patch to @gdb-patches to see how people there think on
this.

-- 
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.


  parent reply	other threads:[~2012-05-23 11:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  8:02 [Bug gdb/14135] New: " qiyao at gcc dot gnu.org
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 [this message]
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-O6oMWH8rRH@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).