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

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

A Friday 14 March 2008 14:35:40, Daniel Jacobowitz wrote:
> 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.
>

I see.  At first I thought it should do what interrupt does, but
then I saw the dbx compatibility version, and just assumed it was it.
(it was calling nothing, and I assumed it was because I didn't have dbx
 mode on ...)

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

It doesn't let you type info registers, because c->name is "registers"
in that case.  It just let's you type "info".  That is useful for the
hook that switches to the top gdb when debugging gdb in gdb.

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

Yeah.  Want me to remove stop and breakpoint?

-- 
Pedro Alves

[-- Attachment #2: remove_break_stop.diff --]
[-- Type: text/x-diff, Size: 799 bytes --]

2008-03-14  Pedro Alves  <pedro@codesourcery.com>

	* top.c (execute_command): Disable break and stop
	commands in async mode.

---
 gdb/top.c |    2 --
 1 file changed, 2 deletions(-)

Index: src/gdb/top.c
===================================================================
--- src.orig/gdb/top.c	2008-03-14 15:30:28.000000000 +0000
+++ src/gdb/top.c	2008-03-14 15:30:38.000000000 +0000
@@ -405,8 +405,6 @@ execute_command (char *p, int from_tty)
 	if (strcmp (c->name, "help") != 0
 	    && strcmp (c->name, "pwd") != 0
 	    && strcmp (c->name, "show") != 0
-	    && strcmp (c->name, "stop") != 0
-	    && strcmp (c->name, "break") != 0
 	    && strcmp (c->name, "info") != 0
 	    && strcmp (c->name, "interrupt") != 0)
 	  error (_("Cannot execute this command while the target is running."));

  reply	other threads:[~2008-03-14 15:33 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
2008-03-14 15:33   ` Pedro Alves [this message]
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=200803141532.58777.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@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