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:05:00 -0000	[thread overview]
Message-ID: <20060123160220.GB16524@nevyn.them.org> (raw)
In-Reply-To: <6541ed4c0601230745o6e063cb6he3ec808e544cd887@mail.gmail.com>

On Mon, Jan 23, 2006 at 04:45:51PM +0100, David Lamy-Charrier wrote:
> Daniel,
> 
> Thanks for your help.
> Here attached is a log between Eclipse and GDB.
> GDB stops on a breakpoint where it is supposed to display a value and
> then continue.
> Unfortunately, it seems that it first informs Eclipse that it stops
> and Eclipse query infos about threads, stack-frame... and the commands
> attached to the breakpoint are never executed.
> 
> When GDB stops on a breakpoint with commands associated, does it
> inform the front-end with MI commands ? if yes, is it after executing
> the commands or before ?

Looks like breakpoint commands are just broken with MI.  I think it has
something to do with the event loop; GDB has too many different ones
still lying around for me to be sure what's going on.  But I think a
call to bpstat_do_actions in mi_execute_command or
mi_execute_command_wrapper might do it.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-23 16:02 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 [this message]
2006-01-23 17:37       ` David Lamy-Charrier
2006-01-23 17:47         ` Daniel Jacobowitz
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=20060123160220.GB16524@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