From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Re: ambiguous linespec decision point
Date: Thu, 01 Dec 2011 16:55:00 -0000 [thread overview]
Message-ID: <20111201165444.GC2781@adacore.com> (raw)
In-Reply-To: <20111201130435.GA3708@redhat.com>
> For what it's worth, I've been using the branch for the past few weeks
> while I've been working on the inline function breakpoint stuff, and
> I've not noticed anything awful.
I think it's very useful to get feedback from real life use - thank you!
--
Joel
next prev parent reply other threads:[~2011-12-01 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 17:10 Tom Tromey
2011-11-30 23:15 ` Sergio Durigan Junior
2011-11-30 23:31 ` Joel Brobecker
2011-12-01 17:10 ` Phil Muldoon
2011-12-01 13:04 ` Gary Benson
2011-12-01 16:55 ` Joel Brobecker [this message]
2011-12-01 21:52 ` Tom Tromey
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=20111201165444.GC2781@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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