This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: target_find_description question
- From: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- To: drow at false dot org (Daniel Jacobowitz)
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 4 Sep 2008 21:16:33 +0200 (CEST)
- Subject: Re: target_find_description question
Daniel Jacobowitz wrote:
> I suppose the easiest thing to do would be to call
> target_find_description right before handle_inferior_event, and rely
> on target_desc_fetched to prevent duplicate work.
Unfortunately, it turns out this doesn't work. Or rather, it works
too well: target_find_description is called after the first stop,
and determines target properties -- while the inferior process is
still executing the shell we're using to start up the real inferior!
So it'll detect e.g. a 32-bit inferior because the shell is 32-bit,
even though the real inferior is a 64-bit application ...
I guess we do need to defer target_find_description until after the
real inferior is started. However, we then have the problem of how
to handle those register/memory accessed in the mean time.
Maybe we can change handle_inferior_event to not do any PC processing
if stop_soon is set?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com