From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add fullname field for MI -break-info command
Date: Thu, 26 Jan 2006 07:10:00 -0000 [thread overview]
Message-ID: <dr9sas$s4b$2@sea.gmane.org> (raw)
In-Reply-To: <20060125134549.GB20856@brasko.net>
Bob Rossi wrote:
>> > > > 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.
Strictly speaking, they are not the same. -break-list is documented to print
list of all breakpoints, while -break-info is documented to print
information about one breakpoint.
- Volodya
next prev parent reply other threads:[~2006-01-26 7:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 16:42 Vladimir Prus
2006-01-24 16:51 ` Bob Rossi
2006-01-25 11:07 ` Vladimir Prus
2006-01-25 12:10 ` Bob Rossi
2006-01-25 12:37 ` Andreas Schwab
2006-01-25 12:50 ` Vladimir Prus
2006-01-25 13:45 ` Bob Rossi
2006-01-26 7:10 ` Vladimir Prus [this message]
2006-01-28 13:10 ` Vladimir Prus
2006-02-01 22:32 ` Daniel Jacobowitz
2006-02-02 7:07 ` Vladimir Prus
2006-02-06 21:55 ` Daniel Jacobowitz
2006-01-24 21:13 ` Daniel Jacobowitz
2006-01-25 13:31 ` Vladimir Prus
2006-01-25 13:46 ` Bob Rossi
2006-01-26 7:20 ` Vladimir Prus
2006-01-25 13:51 ` Daniel Jacobowitz
2006-01-25 17:56 ` Eli Zaretskii
2006-01-24 16:42 Vladimir Prus
2006-01-26 7:06 Nick Roberts
2006-01-26 7:13 Nick Roberts
2006-01-26 11:27 Nick Roberts
2006-01-26 11:44 ` Vladimir Prus
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='dr9sas$s4b$2@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.redhat.com \
/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