This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: enable a couple of useful cli commands in async mode.
- From: Daniel Jacobowitz <drow at false dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 14 Mar 2008 10:35:40 -0400
- Subject: Re: enable a couple of useful cli commands in async mode.
- References: <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