From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "tromey@redhat.com" <tromey@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Daniel Jacobowitz <drow@false.org>,
Pedro Alves <pedro@codesourcery.com>,
teawater <teawater@gmail.com>
Subject: Re: [RFA] Reverse Debugging, 4/5
Date: Tue, 07 Oct 2008 03:15:00 -0000 [thread overview]
Message-ID: <20081007031416.GA28138@adacore.com> (raw)
In-Reply-To: <48EA96E6.40504@vmware.com>
> Erm, yeah, I started to say "I'm open to it", but hey, I just want to
> get my patch in! Surely it will be easy enough to change this to a
> generic setter later?
I don't think I'm the type to let best be the enemy of good, but
in this case, changing the function name wouldn't delay your patch
all that much. So I would insist in that case that you make the
change now rather than later - that way, there's no risk of
forgetting. Or are you concerned that choosing the name might
turn into a long thread?
This being said, I would be totally open to not using the function
at all, and setting b->silent directly. This is a well-documented
standalone flag and I'm personally fine with accessing it directly.
Ideally, I would love for GDB to only use opaque types, but we can
always create the accessor routines if/when we decide to make the
breakpoint structure opaque (opinions welcome).
--
Joel
prev parent reply other threads:[~2008-10-07 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 19:21 Michael Snyder
2008-10-06 21:27 ` Pedro Alves
2008-10-06 21:50 ` Michael Snyder
2008-10-06 21:57 ` Joel Brobecker
2008-10-06 22:18 ` Michael Snyder
2008-10-07 3:18 ` Joel Brobecker
2008-10-06 22:42 ` Tom Tromey
2008-10-06 22:55 ` Michael Snyder
2008-10-06 22:59 ` Tom Tromey
2008-10-07 3:15 ` Joel Brobecker [this message]
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=20081007031416.GA28138@adacore.com \
--to=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
--cc=teawater@gmail.com \
--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