Re: fullname descriptor with -break-list

[Bob Rossi <bob@brasko.net>]

On Fri, Mar 04, 2005 at 08:22:14PM +1300, Nick Roberts wrote:
>  > >>-exec-run
>  > >>^running
>  > >>(gdb) 
>  > >>*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x080486e2",func="myprint",args=[{name="i",value="0"},{name="j",value="0"}],file="myprint.c",line="5"}
>  ...
>  > The way that message is generated is a massive kludge - so the 
>  > underlying code could do with a cleanup - separate the code determining 
>  > why the process stopped from the code printing the stop reason.
> 
> Just a short note for the future:
> 
> As *stopped is asynchronous output and not that of a specific MI command, I
> also think this output should appear even if a CLI command has been invoked.

If you are refering to the fact that you want to know what MI output
command is being sent to you when the command is asynchronous, I
completly agree. In fact, I have plans, if accepted, to put the type of
MI output command directly into the MI output command.

The Apple guys said they patched GDB to behave like this, but only for
asynchronous commands.

Bob Rossi