From: Doug Evans <xdje42@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add some debugging printfs to linux-nat.c
Date: Sat, 13 Sep 2014 23:04:00 -0000 [thread overview]
Message-ID: <m3fvfvqg0p.fsf@sspiff.org> (raw)
In-Reply-To: <m34mwsv6rd.fsf@sspiff.org> (Doug Evans's message of "Sun, 31 Aug 2014 11:44:22 -0700")
Doug Evans <xdje42@gmail.com> writes:
> Hi.
>
> I found these useful when debugging 17247,17314.
>
> 2014-08-31 Doug Evans <xdje42@gmail.com>
>
> * linux-nat.c (wait_lwp): Add debugging printf.
> (linux_nat_wait_1): Ditto.
Committed.
prev parent reply other threads:[~2014-09-13 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 18:45 Doug Evans
2014-09-01 9:09 ` Gary Benson
2014-09-01 17:00 ` Doug Evans
2014-09-13 23:04 ` Doug Evans [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=m3fvfvqg0p.fsf@sspiff.org \
--to=xdje42@gmail.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