Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: lgustavo@codesourcery.com
Cc: Pedro Alves <palves@redhat.com>,
	ali_anwar <ali_anwar@codesourcery.com>,
	       dje@google.com, Yao Qi <yao@codesourcery.com>,
	       gdb-patches@sourceware.org
Subject: Re: Patch to propagate GDB's knowledge of the executing state to frontend
Date: Tue, 13 Nov 2012 21:57:00 -0000	[thread overview]
Message-ID: <87wqxp414y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <509D8B21.2040804@codesourcery.com> (Luis Machado's message of	"Fri, 09 Nov 2012 21:00:49 -0200")

Luis> Should frontends relying on MI information treat ^error specially and
Luis> not look for any *stopped records?

I don't know the answer to this.  I did find this though:

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

I tend to think it would be cleanest if gdb were to emit a *stopped in
case of error -- but only if it previously emitted *running.  I don't
know how feasible this is.

Luis> The MI specification gives room for slightly different interpretations
Luis> unfortunately.

For me, the text for "*running" is pretty clear:

     The frontend should assume that no interaction with a
     running thread is possible after this notification is produced.

I'm curious where the text is that gives room for another approach.

Tom


  parent reply	other threads:[~2012-11-13 21:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 11:10 ali_anwar
2012-10-30  6:20 ` Yao Qi
2012-10-30 11:53   ` ali_anwar
2012-11-02 10:28     ` ali_anwar
2012-11-02 11:47       ` Yao Qi
2012-11-02 12:24     ` ali_anwar
2012-11-02 16:15   ` dje
2012-11-02 18:47     ` ali_anwar
2012-11-09 19:31       ` Anwar, Ali
2012-11-09 19:42         ` Pedro Alves
2012-11-09 19:48       ` Pedro Alves
2012-11-09 23:00         ` Luis Machado
2012-11-09 23:02           ` Luis Machado
2012-11-13 21:57           ` Tom Tromey [this message]
2012-11-13 22:23             ` Luis Machado
2012-11-14 18:29               ` Pedro Alves
2012-11-15 21:23                 ` Tom Tromey

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=87wqxp414y.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ali_anwar@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.com \
    --cc=yao@codesourcery.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