From: Bob Rossi <bob@brasko.net>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add fullname field for MI -break-info command
Date: Wed, 25 Jan 2006 12:10:00 -0000 [thread overview]
Message-ID: <20060125121030.GJ28357@brasko.net> (raw)
In-Reply-To: <dr7m5j$gcp$1@sea.gmane.org>
On Wed, Jan 25, 2006 at 02:07:28PM +0300, Vladimir Prus wrote:
> Bob Rossi wrote:
>
> > On Tue, Jan 24, 2006 at 07:32:15PM +0300, Vladimir Prus wrote:
> >>
> >> Hello!
> >>
> >> The attached patch adds the "fullname" field to the output of MI
> >> -break-info command.
> >
> > The patch seems good to me at first glance. However, you should also
> > update the testsuite, and send in the patch for that as well.
>
> I'm looking into this right now, and have a question. Inside the test, I
> need to get the absolute path to the source file. If I use:
>
> "${srcdir}/${subdir}/${srcfile}"
>
> the result is:
>
> "../.././gdb/testsuite/gdb.mi/basics.c"
No, please user ${fullname_syntax}${srcfile}. That will provide you with
a regular expression that matches the fullname, and end in the source
file you are interestd in. You can see how this is done in
mi2-stack.exp.
> while output of gdb has absolute path name. So: how do I convert relative
> path to an absolute one inside a test? (I don't know anything about Tcl, so
> it's not obvious for me).
>
> BTW, it would be nice in gdbint explicitly said how one can run a specific
> test from testsuite.
Yeah, I totally agree. I forget every time. Try 'runtest mi2-stack.exp',
to run just that test.
> > 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?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2006-01-25 12: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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 11:27 Nick Roberts
2006-01-26 11:44 ` Vladimir Prus
2006-01-26 7:13 Nick Roberts
2006-01-26 7:06 Nick Roberts
2006-01-24 16:42 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=20060125121030.GJ28357@brasko.net \
--to=bob@brasko.net \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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