From: Mark Kettenis <kettenis@wins.uva.nl>
To: kevinb@cygnus.com
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add control variable for debug output to linux threads
Date: Sat, 28 Apr 2001 00:42:00 -0000 [thread overview]
Message-ID: <200104280742.f3S7g2q00251@delius.kettenis.local> (raw)
In-Reply-To: <1010427212615.ZM20249@ocotillo.lan>
Date: Fri, 27 Apr 2001 14:26:15 -0700
From: Kevin Buettner <kevinb@cygnus.com>
Cc: Mark Kettenis <kettenis@science.uva.nl>, gdb-patches@sources.redhat.com
Content-Type: text/plain; charset=us-ascii
On Apr 26, 4:13pm, Michael Snyder wrote:
> This patch replaces your DEBUG macro with a runtime variable that is
> settable by a user command. At some recent check-in, you left the
> DEBUG macro turned on, and users have been asking about the extra
> messages.
>
> 2001-04-26 Michael Snyder <msnyder@redhat.com>
>
> * thread-db.c (_initialize_thread_db): Add set/show command
> "debug-linux-threads" for debugging output.
> * lin-lwp.c (various): Use global "debug_linux_threads to
> turn on extra debugging output.
Michael,
I have problems with your patch since it does a bit more than
advertised.
Apart from that, I'm having some trouble with the fact that the
set/show command is added to thread-db.c (the user threads library
layer, that in principle isn't Linux-specific) while the debug code
that it enables is code for the Linux-specific kernel threads (LWP)
support code that lives in lin-lwp.c.
Michael, may I suggest reverting this patch and discussing it next
week? I've got a train to catch now, so I'm a bit in a hurry.
Mark
next prev parent reply other threads:[~2001-04-28 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200104191140.f3JBemM02725@delius.kettenis.local>
[not found] ` <3AE8AB9E.DC0E5BB0@cygnus.com>
2001-04-26 21:05 ` Andrew Cagney
[not found] ` <1010427212615.ZM20249@ocotillo.lan>
2001-04-28 0:42 ` Mark Kettenis [this message]
2001-04-30 10:31 ` Michael Snyder
2001-04-30 10:29 ` 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=200104280742.f3S7g2q00251@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=gdb-patches@sources.redhat.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