Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Chris Moller <cmoller@redhat.com>
Cc: "gdb-patches@sourceware.org" <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:35:00 -0000	[thread overview]
Message-ID: <4BCE01E0.8020401@vmware.com> (raw)
In-Reply-To: <4BCE00EC.9050300@redhat.com>

Chris Moller wrote:
> On 04/20/10 15:27, Michael Snyder wrote:
>> Chris Moller wrote:
>>> On 04/20/10 15:23, Michael Snyder wrote:
>>>> Chris Moller wrote:
>>>>> Allows the argument to rbreak to specify a file to which to limit 
>>>>> the regex search for function names.  This allows, e.g.,
>>>>>
>>>>>     rbr file.c : .*
>>>>>
>>>>> which sets bps in every function in the specified file.
>>>> I like the idea very much, but I don't quite understand
>>>> the extra white space?
>>>>
>>>>
>>> The whitespace is optional, included just for clarity.  All the WS is 
>>> stripped from both the filename and the regex before they're passed 
>>> to the search.
>> Thanks.
>>
>> Worth a doco mention?
> 
> Sure, if that's what folks want, I'll add some words to gdb.texinfo and 
> refcard.tex

As far as the code goes, I don't think we allow single-line blocks,
and I personally don't care much for such short variable names that
don't convey much about what they are for...


  reply	other threads:[~2010-04-20 19:35 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 [this message]
2010-04-20 19:44 ` Tom Tromey
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=4BCE01E0.8020401@vmware.com \
    --to=msnyder@vmware.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