Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: Re: replace debug_linux_nat_async with debug_linux_nat ?
Date: Tue, 03 May 2011 21:34:00 -0000	[thread overview]
Message-ID: <201105032234.36317.pedro@codesourcery.com> (raw)
In-Reply-To: <20110503202514.5241E2461A9@ruffy.mtv.corp.google.com>

On Tuesday 03 May 2011 21:25:14, Doug Evans wrote:
> 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.

It's considerably more noisy, and doesn't help much
sync debugging, but I won't mind.  Especially since
I'd like to flip to async on by default :-)  (needs
fixing some regressions compared to sync mode first though).

Note some tests rely on "set debug lin-lwp", so you'll
most probably need to fix them.

-- 
Pedro Alves


  reply	other threads:[~2011-05-03 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 20:25 Doug Evans
2011-05-03 21:34 ` Pedro Alves [this message]
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=201105032234.36317.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=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