From: "J. Johnston" <jjohnstn@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb@sources.redhat.com
Subject: Re: prev_pc problem on ia64
Date: Mon, 05 May 2003 19:57:00 -0000 [thread overview]
Message-ID: <3EB6C225.6090804@redhat.com> (raw)
In-Reply-To: <3E9CCB50.5000908@redhat.com>
Andrew Cagney wrote:
>>>
>>> > I tried to use target_has_execution but that did not work. The error
>>> > I get is that the process does not exist. The read_pc() routine
>>> for the ia64 is doing
>>> > a read_register_pid() and it appears that the inferior_ptid is not
>>> set up
>>> > at a time when target_has_execution is set to true.
>>>
>>> target_has_execution doesn't mean that the target is executing. It is
>>> a total misnomer to indicate that the gdb target stratum is capable of
>>> execution. I think what you want is target_has_registers.
>>
>
>
>> Arrrgh! That problem, core file's also has registers ... so right
>> theory, I've no idea on which thing to use in the test though.
>
>
> Hmm, ... but at least target_has_registers should only be true when the
> target really does have the registers available. I guess try it.
>
> Andrew
>
>
There is a problem in my choice of where to set prev_pc. The inferior is not guaranteed
to be stopped when init_execution_control_state() is called so ptrace can fail when
asked to fetch the pc register.
I believe I have found a solution that avoids this problem by refreshing prev_pc in proceed()
just prior to resuming. I will post a patch shortly.
-- Jeff J.
prev parent reply other threads:[~2003-05-05 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 22:21 J. Johnston
2003-04-14 20:17 ` Elena Zannoni
2003-04-14 20:42 ` J. Johnston
2003-04-15 22:06 ` Andrew Cagney
2003-04-16 0:04 ` J. Johnston
2003-04-16 1:35 ` Elena Zannoni
2003-04-16 1:56 ` Andrew Cagney
2003-04-16 3:17 ` Andrew Cagney
2003-04-16 15:14 ` J. Johnston
2003-05-05 19:57 ` J. Johnston [this message]
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=3EB6C225.6090804@redhat.com \
--to=jjohnstn@redhat.com \
--cc=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).