(maybe) Async mode failures on PPC

Pedro Alves pedro@codesourcery.com
Mon Jul 14 16:58:00 GMT 2008

Hi Luis,

On Monday 14 July 2008 17:31:42, Luis Machado wrote:
> Steps to reproduce this failure:
> 1 - Load the watchpoint.exp test binary into gdb.
> 2 - start it and next over a few lines.

I can't reproduce it on x86 (sync or async), neither with your
recipe or by running the watchpoint.exp test.


The "Target is executing" notice comes from frame.c:get_current_frame.

I couldn't figure out for sure from your description of the
problem if this only happens in async, or if it happen in sync as well,
but I understood async only.

Why is GDB trying to get the current frame of an executing
thread, or why does GDB think that the current thread is
executing at this point, if it isn't?

Can you do a bit of debugging and figure out what is the
code path that ended up triggering the first error?
get_current_frame is called from too many places to be able
to do an educated guess.

Pedro Alves

More information about the Gdb mailing list