From: Matt Rice <ratmice@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb@sourceware.org
Subject: Re: Toward multicore GDB - Set theory
Date: Tue, 08 Nov 2011 05:17:00 -0000 [thread overview]
Message-ID: <CACTLOFp0qgnmcMPW4+nkbxM5nFJcWPMmezUVNFVLE0ryBYk8zQ@mail.gmail.com> (raw)
In-Reply-To: <m34nyksyxf.fsf@fleche.redhat.com>
On Thu, Nov 3, 2011 at 2:01 PM, Tom Tromey <tromey@redhat.com> wrote:
> (gdb) break [0-13] function # "semi-prefix"
I personally prefer to avoid this one because the square brackets it
would seem difficult to
disambiguate between thread sets and objective-c methods, at least
when naming threads is added.
next prev parent reply other threads:[~2011-11-08 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 0:04 Stan Shebs
2011-11-03 21:01 ` Tom Tromey
2011-11-04 13:20 ` Pedro Alves
2011-11-07 17:38 ` Joel Brobecker
2011-11-08 1:14 ` Daniel Jacobowitz
2011-11-08 5:17 ` Matt Rice [this message]
2011-11-08 14:50 ` Pedro Alves
2011-11-08 15:04 ` Tom Tromey
2011-11-08 15:45 ` Pedro Alves
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=CACTLOFp0qgnmcMPW4+nkbxM5nFJcWPMmezUVNFVLE0ryBYk8zQ@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).