Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: PILLON Julien <julien.pillon@alyotech.fr>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: Paul Koning <Paul_Koning@Dell.com>,
	"gdb@sourceware.org" 	<gdb@sourceware.org>
Subject: RE : RE : User level threads debugging with GDB
Date: Fri, 09 Apr 2010 13:54:00 -0000	[thread overview]
Message-ID: <06A7AD4E92172446ADDEB44F8A5D5C101CA8246BF2@ARE01.alyotech.fr> (raw)
In-Reply-To: <20100409134324.GA16597@caradoc.them.org>

Ok, I thought it was really full used...
So if I go on implementing libthread_db, I'll have to modify GDB also...
I think one day (...) I'll manage to understand the deeps of GDB... ^^
Thanks

Julien

________________________________________
De : Daniel Jacobowitz [dan@codesourcery.com]
Date d'envoi : vendredi 9 avril 2010 15:43
À : PILLON Julien
Cc : Paul Koning; gdb@sourceware.org
Objet : Re: RE : User level threads debugging with GDB

On Fri, Apr 09, 2010 at 03:04:28PM +0200, PILLON Julien wrote:
> Thank you for your answer.
> The fact is that I don't want to make big modification to GDB... So I think  I'll go on implementing a libthread_db (with this method, it will be compatible with future (and previous ?) versions of GDB )

This is not likely to work.  Linux thread debugging uses a little bit
of the libthread_db but also knows a great deal about native OS
threads.  There is also some libthread_db code for Solaris, but it's
tied together with procfs support.  There is no generic libthread_db
layer.

--
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2010-04-09 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  8:12 PILLON Julien
2010-04-09 10:49 ` Paul Koning
2010-04-09 13:04   ` RE : " PILLON Julien
2010-04-09 13:43     ` Daniel Jacobowitz
2010-04-09 13:54       ` PILLON Julien [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=06A7AD4E92172446ADDEB44F8A5D5C101CA8246BF2@ARE01.alyotech.fr \
    --to=julien.pillon@alyotech.fr \
    --cc=Paul_Koning@Dell.com \
    --cc=dan@codesourcery.com \
    --cc=gdb@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