This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Add fullname field for MI -break-info command


> > > > Also, don't forget about the documentation.
> > >
> > > Well, at the moment the -break-info command is not documented at all, so
> > > there's no place where I can add the extra "fullname" field.
> >
> > Hmm, there is a section in the gdb.texinfo manual that says
> >     @c REDUNDANT???
> >     Get information about a single breakpoint.
> > how is this command useful, instead of just using -break-list?
> 
> 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, 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.

For -file-list-exec-source-files I used this path as an example,
    @smallexample
    (@value{GDBP})
    123-file-list-exec-source-file
    123^done,line="1",file="foo.c",fullname="/home/bar/foo.c"
    (@value{GDBP})
    @end smallexample

so, yes, something like you have is OK. 

Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]