From: Mark Kettenis <kettenis@wins.uva.nl>
To: msnyder@cygnus.com
Cc: gdb-patches@sourceware.cygnus.com, cagney@cygnus.com, kevinb@cygnus.com
Subject: Re: [rfa] Printf debugging output in lin-lwp.c
Date: Mon, 30 Apr 2001 12:06:00 -0000 [thread overview]
Message-ID: <200104301906.f3UJ6SJ00484@delius.kettenis.local> (raw)
In-Reply-To: <3AEDAF16.8D27C455@cygnus.com>
Date: Mon, 30 Apr 2001 11:29:42 -0700
From: Michael Snyder <msnyder@cygnus.com>
Mark, how about this?
Looks good to me (except for the formatting of the ChangeLog entry :-)).
[In reply to your other mail]
Well, I figured we would from time to time need some similar
printf/debug code in thread-db too. As for it not being
linux-specific, that was the original hope, but I don't
really imagine it happening anytime soon.
I think a seperate switch for debug code in thread-db would be
appropriate.
Mark
next prev parent reply other threads:[~2001-04-30 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 11:34 Michael Snyder
2001-04-30 12:06 ` Mark Kettenis [this message]
2001-04-30 18:14 ` Andrew Cagney
2001-05-01 13:38 ` [patch] change printf to fprintf_unfiltered Michael Snyder
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=200104301906.f3UJ6SJ00484@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=cagney@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=kevinb@cygnus.com \
--cc=msnyder@cygnus.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