From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: replace debug_linux_nat_async with debug_linux_nat ?
Date: Tue, 03 May 2011 20:25:00 -0000 [thread overview]
Message-ID: <20110503202514.5241E2461A9@ruffy.mtv.corp.google.com> (raw)
Hi.
Anyone mind if I delete linux-nat.c:debug_linux_nat_async
and replace it with debug_linux_nat?
I've been in some sessions where I turn the latter on
only to find I also want the former, and from what I read
I pretty much always want both.
next reply other threads:[~2011-05-03 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 20:25 Doug Evans [this message]
2011-05-03 21:34 ` Pedro Alves
2011-05-05 17:27 ` Tom Tromey
2011-05-09 19:11 ` Doug Evans
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=20110503202514.5241E2461A9@ruffy.mtv.corp.google.com \
--to=dje@google.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