[PATCH] Add fullname field for MI -break-info command
Nick Roberts
nickrob@snap.net.nz
Thu Jan 26 07:06:00 GMT 2006
I've probably not followed the whole thread, but here goes...
> > Hmm, so I should update all examples of "-break-list" output as well? What
> > path should I put there? Is /home/foo/bar/<whatever-the-source-file-is>.c
> > fine?
> Yes, please update the documentation for -break-list,
-break-insert also uses print_one_breakpoint so I guess that should be
updated
> and I don't know
> if you should even bother with -break-info. I still don't know if that
> command should exist if it's identical to -break-list. A machine
> interface does not need 2 commands for the same functionatlity, IMO.
I don't know if its needed either but now its there I don't see any
point in removing it (if it ain't broke don't fix it).
Also the doc says:
The `-break-info' Command
Synopsis
-break-info BREAKPOINT
Get information about a single breakpoint.
GDB command
The corresponding GDB command is `info break BREAKPOINT'.
Example
N.A.
and
Also note that the commands with a non-available example (N.A.) are not
yet implemented.
but -break-info clearly has been implemented.
Nick http://www.inet.net.nz/~nickrob
More information about the Gdb-patches
mailing list