Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix internal-error on dead LWPs with no associated thread
Date: Mon, 29 Jun 2009 21:42:00 -0000	[thread overview]
Message-ID: <200906292243.24272.pedro@codesourcery.com> (raw)
In-Reply-To: <20090629213333.GA3295@host0.dyn.jankratochvil.net>

On Monday 29 June 2009 22:33:33, Jan Kratochvil wrote:
> I do not share this opinion - not attaching short-lived threads should not be
> allowed for performance reasons.  When such short-lived thread crashes GDB
> should catch such crash.
> 

Sorry, this makes no sense.  GDB is automaticaly attached to cloned
threads.  You won't miss any crash.  You're thinking of discovering
threads with thread_db?

The performance issue is related with communicating the
new-thread/thread-exited to the frontend, or with printing it to
the screen with printf_unfiltered, not related to the thread
management per-se.

-- 
Pedro Alves


  reply	other threads:[~2009-06-29 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 10:09 Jan Kratochvil
2009-06-29 10:35 ` Pedro Alves
2009-06-29 17:51   ` Jan Kratochvil
2009-06-29 18:30     ` Pedro Alves
2009-06-29 18:59       ` Jan Kratochvil
2009-06-29 18:31     ` Jan Kratochvil
2009-06-29 18:41       ` Pedro Alves
2009-06-29 21:35         ` Jan Kratochvil
2009-06-29 21:42           ` Pedro Alves [this message]
2009-06-29 21:48             ` Jan Kratochvil

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=200906292243.24272.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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