From: Tom Tromey <tromey@redhat.com>
To: Chris Moller <cmoller@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PR10179, Add support to set a breakpoint at every function in a file
Date: Tue, 20 Apr 2010 19:44:00 -0000 [thread overview]
Message-ID: <m3d3xtgb95.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BCDFEA5.9090501@redhat.com> (Chris Moller's message of "Tue, 20 Apr 2010 15:21:09 -0400")
>>>>> "Chris" == Chris Moller <cmoller@redhat.com> writes:
Chris> +2010-04-20 Chris Moller <cmoller@redhat.com>
Chris> + PR filename-filtered rbreak/10179
This particular syntax probably won't have the desired effect.
The commit script only recognizes a few specific formats.
It should be just "PR category/NNNN", like "PR breakpoints/10179".
Chris> + * symtab.c (rbreak_command): Added code to detect a filename
Chris> + specification in conjunction with the function specification (in
Chris> + the form of "filename : regex", checking to make sure that the
Chris> + colon isn't part of a qualified function name). If the filename
Chris> + is discovered, it's passed to search_symbols.
The description is too long. It should only describe what is changing.
Any further details belong in the code.
Chris> + char * colon = strchr (regexp, ':');
Extra space after "*".
Chris> + int ix;
Chris> + char * ta;
I agree with Michael about the names.
Chris> + while (isspace (ta[ix])) { ta[ix--] = 0; }
As Michael, this isn't our style.
This requires a documentation and NEWS patch.
Tom
next prev parent reply other threads:[~2010-04-20 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 19:21 Chris Moller
2010-04-20 19:23 ` Michael Snyder
2010-04-20 19:25 ` Chris Moller
2010-04-20 19:27 ` Michael Snyder
2010-04-20 19:30 ` Chris Moller
2010-04-20 19:35 ` Michael Snyder
2010-04-20 19:44 ` Tom Tromey [this message]
2010-04-21 2:56 ` Chris Moller
2010-04-21 21:24 ` Michael Snyder
2010-04-21 22:27 ` Tom Tromey
2010-04-23 9:30 ` Eli Zaretskii
2010-04-23 12:09 ` Chris Moller
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=m3d3xtgb95.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cmoller@redhat.com \
--cc=gdb-patches@sourceware.org \
/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