From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: expected behavior of GNU/Linux gcore and corefiles
Date: Sun, 02 Mar 2003 03:46:00 -0000 [thread overview]
Message-ID: <20030302034653.GA14491@nevyn.them.org> (raw)
In-Reply-To: <20030302033900.GA14335@nevyn.them.org>
On Sat, Mar 01, 2003 at 10:39:00PM -0500, Daniel Jacobowitz wrote:
> > My instincts tell me that, to completly implement the above
> > functionality, GDB is always going to need libthread-db. If GDB could
> > implement the above on a core file without using libthread-db, then GDB
> > could also implement the above on a live target also without using
> > libthread-db. This is because a core file is always going to contain a
> > subset of the information made available via ptrace et.al.
Oh, and one other thing that I like to mention when this comes up. My
previous message was the implementation issues involved; this one's the
motivational issue. Thread_db is not, and can't/shouldn't be,
available in a cross environment. We have done a lot of work to make
GDB read corefiles in a cross environment; and at MontaVista we've seen
a large demand for this functionality from our customers. So using
thread_db with corefiles doesn't meet our (GDB developers') goals, I
think.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-02 3:46 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 [this message]
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
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=20030302034653.GA14491@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.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