This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Does gdb 5.2 work with statically linked thread application under Linux?
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: "H . J . Lu" <hjl at lucon dot org>
- Cc: GDB <gdb at sources dot redhat dot com>
- Date: Thu, 7 Mar 2002 02:48:41 -0500
- Subject: Re: Does gdb 5.2 work with statically linked thread application under Linux?
- References: <20020306233050.A31848@lucon.org>
On Wed, Mar 06, 2002 at 11:30:50PM -0800, H . J . Lu wrote:
> Does gdb 5.2 work with statically linked thread application under
> Linux? It doesn't work for me at all. It doesn't know any thread.
> I have a patch which works for gdb 5.1. Now it doesn't work for 5.2
> anymore.
My fault, I think.
The problem is that in a dynamically linked binary
thread_db_new_objfile will be called for every library is loaded. At
this point current_target is "child", so target_has_execution is true.
But with a static binary, the first time the function is called objfile
is NULL, and the second time current_target is "exec" (which has
target_has_execution set false).
Perhaps target_has_execution was not the right check after all, if
"exec" has it set false (which makes fairly little sense to me...) or
perhaps we need to call the hook again later. Michael, any idea?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer