From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: expected behavior of GNU/Linux gcore and corefiles
Date: Sun, 02 Mar 2003 20:32:00 -0000 [thread overview]
Message-ID: <20030302203222.GB24948@nevyn.them.org> (raw)
In-Reply-To: <3E6266DB.9020704@redhat.com>
On Sun, Mar 02, 2003 at 03:17:31PM -0500, Andrew Cagney wrote:
> Dig dig, this has come up before. Up until this change:
>
> >2002-01-04 Daniel Jacobowitz <drow@mvista.com>
> >
> > * thread-db.c (thread_db_new_objfile): Do not enable thread_db
> > for core files.
> >
>
> GDB was barfing when trying to load the thread DB. Looking back through
> that thread, part of the problem appears to have stemed from GDB
> thinking that the GNU/Linux core file contained threads instead of LWPs :-(
>
> Andrew
>
> http://sources.redhat.com/ml/gdb-patches/2002-01/msg00017.html
> http://sources.redhat.com/ml/gdb-patches/2001-12/msg00345.html
Yep. Among other things the problems arise because thread_db passes
requests to lin-lwp instead of properly along the target stack; lin-lwp
should be sitting in the "process" slot on the target stack.
There are also load/unload issues; observers are the perfect way to fix
that.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-03-02 20:32 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
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 [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=20030302203222.GB24948@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