Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Chris Demetriou <cgd@google.com>,  gdb-patches@sources.redhat.com
Subject: Re: [RFA] 'set print thread-events' to control printing of thread start/exit messages
Date: Thu, 20 Dec 2007 15:46:00 -0000	[thread overview]
Message-ID: <200712201823.48979.vladimir@codesourcery.com> (raw)
In-Reply-To: <20071220134556.GA7244@caradoc.them.org>

On Thursday 20 December 2007 16:45:56 Daniel Jacobowitz wrote:
> On Thu, Dec 20, 2007 at 12:03:17AM -0800, Chris Demetriou wrote:
> > [hi!  long time no see!]
> 
> No kidding!
> 
> > The attached patch makes the printing of thread start/exit messages on
> > Linux configurable via 'set print thread-events'.  (A coworker
> > commented that for the benchmarks he was trying to debug, printing of
> > thread start/exit messages was ... quite tedious.  And i figured a
> > patch would be ... quite straightforward.)
> > 
> > I'm ambivalent about the name of the new option, and the location of
> > the option in the docs.  I'm willing to listen to suggestions
> > (especially from approvers! 8-) of better alternatives.
> 
> Hi Chris, meet Vladimir.  Hi Vladimir, meet Chris.  

Hi Chris!

> I suggest one of 
> you combine this with Vladimir's recently pending patch to unify new
> thread printing in a single place for all targets.

I can do this, if Chris does not mind.

- Volodya


  reply	other threads:[~2007-12-20 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 13:46 Chris Demetriou
2007-12-20 14:00 ` Daniel Jacobowitz
2007-12-20 15:46   ` Vladimir Prus [this message]
2007-12-20 16:00     ` Chris Demetriou
2007-12-21 16:19 ` Eli Zaretskii

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=200712201823.48979.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=cgd@google.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.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