This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: expected behavior of GNU/Linux gcore and corefiles
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Sun, 2 Mar 2003 15:32:22 -0500
- Subject: Re: expected behavior of GNU/Linux gcore and corefiles
- References: <3E617797.5000704@redhat.com> <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 at mvista dot 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