Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org,  luisgpm@linux.vnet.ibm.com
Subject: Re: (maybe) Async mode failures on PPC
Date: Mon, 14 Jul 2008 16:58:00 -0000	[thread overview]
Message-ID: <200807141757.51890.pedro@codesourcery.com> (raw)
In-Reply-To: <1216053102.2607.13.camel@gargoyle>

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


  reply	other threads:[~2008-07-14 16:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 15:45 Luis Machado
2008-07-14 16:32 ` Luis Machado
2008-07-14 16:58   ` Pedro Alves [this message]
2008-07-14 17:07     ` Luis Machado
2008-07-15 14:47       ` Luis Machado
2008-07-15 16:34         ` Pedro Alves
2008-07-15 16:40           ` Daniel Jacobowitz
2008-07-15 16:42             ` Pedro Alves
2008-07-15 16:45         ` Luis Machado
2008-07-15 16:49           ` Daniel Jacobowitz
2008-07-15 17:30             ` Luis Machado
2008-07-14 21:37     ` Andreas Schwab

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=200807141757.51890.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.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