Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: David Lamy-Charrier <david.lamy@gmail.com>
Cc: GDB List <gdb@sources.redhat.com>
Subject: Re: breakpoint commands no more working due to MI front-end
Date: Mon, 23 Jan 2006 17:47:00 -0000	[thread overview]
Message-ID: <20060123173657.GA20650@nevyn.them.org> (raw)
In-Reply-To: <6541ed4c0601230905q50e4a6b1rc8e4659b63589633@mail.gmail.com>

On Mon, Jan 23, 2006 at 06:05:45PM +0100, David Lamy-Charrier wrote:
> Thanks Daniel for the idea, I am going to try it.
> 
> But if I am right, mi_execute_command is called to handle MI commands
> from the front-end, so it is already too late to execute the commands
> associated with the breakpoint.
> The commands should have been executed before and the front-end should
> even not be notified that GDB stopped and continued, no?

That would require a much bigger change to the way GDB works.  We've
been talking about some related changes; the general question is
whether the MI front end should know that something other than itself
has caused the inferior to change state.  This is vital to have
multiple interpreters active at the same time.

Given how MI works and is defined today, I don't think breakpoint
commands make a whole lot of sense: your front end should supply the
commands when it sees the breakpoint.  Is there a reason you can't make
CDT do that?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-23 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 11:32 David Lamy-Charrier
2006-01-23 13:51 ` Daniel Jacobowitz
2006-01-23 15:52   ` David Lamy-Charrier
2006-01-23 17:05     ` Daniel Jacobowitz
2006-01-23 17:37       ` David Lamy-Charrier
2006-01-23 17:47         ` Daniel Jacobowitz [this message]
2006-01-23 17:53           ` David Lamy-Charrier
2006-01-23 17:58           ` Bob Rossi
2006-01-23 19:34             ` Daniel Jacobowitz
2006-01-24  4:48               ` Jim Ingham

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=20060123173657.GA20650@nevyn.them.org \
    --to=drow@false.org \
    --cc=david.lamy@gmail.com \
    --cc=gdb@sources.redhat.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