Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: enable a couple of useful cli commands in async mode.
Date: Fri, 14 Mar 2008 14:36:00 -0000	[thread overview]
Message-ID: <20080314143540.GA18511@caradoc.them.org> (raw)
In-Reply-To: <200803140759.55397.pedro@codesourcery.com>

On Fri, Mar 14, 2008 at 07:59:55AM +0000, Pedro Alves wrote:
> This is needed to test/develop async with CLI.  The info info command is
> very useful to debug gdb itself, and the interrupt command is needed to be
> able to SIGINT the target.  Without it, the user is trapped in the hole
> of wanting to quit, but gdb complaining "I can't do that Dave" while  the 
> target is running.  "stop" is there already, so I added break too,
> although it doesn't work yet.
> 
> CLI command filtering this way is a gross hack that needs cleaning
> up anyway.  Since noone is using this currently, I went ahead and installed
> as obvious.

I'm confused by your choices.  "stop" is not the command you think it
is.  There's a "stop_command" in breakpoint.c but that's the
DBX-compatibility version of "break".  The command "stop" doesn't
do anything; it's only there for hook-stop.

Also, how can we enable "info"?  That will let you type "info regs"
while the target is running; does something produce a useful error
further down?

"interrupt" makes sense.  In fact I think this is what whoever added
"stop" actually meant to add.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-14 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  8:00 Pedro Alves
2008-03-14 14:36 ` Daniel Jacobowitz [this message]
2008-03-14 15:33   ` Pedro Alves
2008-03-14 15:43     ` Daniel Jacobowitz

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=20080314143540.GA18511@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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