Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: expected behavior of GNU/Linux gcore and corefiles
Date: Sun, 02 Mar 2003 20:03:00 -0000	[thread overview]
Message-ID: <3E6263F8.7040706@redhat.com> (raw)
In-Reply-To: <20030302183257.GA21281@nevyn.them.org>


>> 
>> If that position means precluding certain native-only functionality?
> 
> 
> Not exactly; if that native-only functionality precludes keeping what
> we have now for non-thread_db setups and extending it.



> For instance, I
> think we should always be able to print LWP state (assuming a 1-1
> mapping when we have no thread_db to ask for more information).  And I
> think we should add support for TLS based only on LWPs, since it's not
> dependent on the thread manager.  If we can't "info mutex" on a cross
> corefile, well, that's the same as now.

To draw this back to the original post.  What of a native GDB loading 
libthread-db over a core file to determine thread IDs and TLS?

Andrew



  reply	other threads:[~2003-03-02 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02  3:14 Andrew Cagney
2003-03-02  3:39 ` Daniel Jacobowitz
2003-03-02  3:46   ` Daniel Jacobowitz
2003-03-02 15:53     ` Andrew Cagney
2003-03-02 17:09       ` Daniel Jacobowitz
2003-03-02 18:29         ` Andrew Cagney
2003-03-02 18:33           ` Daniel Jacobowitz
2003-03-02 20:03             ` Andrew Cagney [this message]
2003-03-02 20:31               ` Daniel Jacobowitz
2003-03-02 15:25   ` Andrew Cagney
2003-03-02 20:15 ` Andrew Cagney
2003-03-02 20:32   ` Daniel Jacobowitz

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=3E6263F8.7040706@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@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