public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Grant Edwards <grante@visi.com>
Cc: <insight@sources.redhat.com>
Subject: Re: No step button using insight w/ remote target.
Date: Mon, 19 Nov 2001 12:55:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0111191249421.16197-100000@makita.cygnus.com> (raw)
Message-ID: <20011119125500.91mljf9-S93FMppAkDUqgnIfJ1FneQ-7R-HNhlZFLRs@z> (raw)
In-Reply-To: <20011119145348.A26837@visi.com>

On Mon, 19 Nov 2001, Grant Edwards wrote:

> 829       if (target_has_execution && ! ptid_equal (inferior_ptid, null_ptid))
> Value returned is $3 = 1
> (gdb) print inferior_ptid
> $4 = {pid = 0, lwp = 0, tid = 0}
> (gdb) print null_ptid
> $5 = {pid = 0, lwp = 0, tid = 0}
> (gdb) print target_has_execution
> No symbol "target_has_execution" in current context.
> (gdb)
>
> "target_has_execution" is presumably a macro?

Yes:
#define target_has_execution    \
     (current_target.to_has_execution)

> Anyway, inferior_ptid _is_ null_ptid, so that's probably the
> issue.  The "value returned" bit is from which I did a "finish"
> to get back from ptid_equal(), IOW, ptid_equal() returned 1.

I'm not so certain that there is something wrong with your stub. Let's
back up a little and see if the ptid is ever created...

If you step through remote_open_1, does the following line ever get
executed?


  /* Without this, some commands which require an active target (such
     as kill) won't work.  This variable serves (at least) double duty
     as both the pid of the target process (if it has such), and as a
     flag indicating that a target is active.  These functions should
     be split out into seperate variables, especially since GDB will
     someday have a notion of debugging several processes.  */

  inferior_ptid = pid_to_ptid (MAGIC_NULL_PID);

Keith


  reply	other threads:[~2001-11-19 12:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 15:19 Grant Edwards
2001-10-01  8:25 ` Fernando Nasser
2001-10-02 14:22   ` Grant Edwards
2001-11-15 15:46     ` Grant Edwards
2001-10-02 15:40   ` Grant Edwards
2001-11-19  8:32     ` Grant Edwards
2001-11-12  7:13   ` Fernando Nasser
2001-10-02 16:10 ` Keith Seitz
2001-10-02 20:18   ` Grant Edwards
2001-10-03  9:37     ` Keith Seitz
2001-10-03 10:54       ` Grant Edwards
2001-10-03 11:09         ` Keith Seitz [this message]
2001-10-03 11:20           ` Grant Edwards
2001-10-03 11:47             ` Keith Seitz
2001-10-03 13:22               ` Grant Edwards
2001-10-03 14:03                 ` Keith Seitz
2001-10-03 15:50                   ` Grant Edwards
2001-11-19 14:12                     ` Grant Edwards
2001-11-19 13:28                   ` Keith Seitz
2001-11-19 13:19                 ` Grant Edwards
2001-10-03 16:31               ` Grant Edwards
2001-10-04 11:28                 ` Grant Edwards
2001-11-20 16:16                   ` Grant Edwards
2001-11-19 14:39                 ` Grant Edwards
2001-11-19 13:05               ` Keith Seitz
2001-11-19 13:03             ` Grant Edwards
2001-11-19 12:55           ` Keith Seitz
2001-11-19 12:49         ` Grant Edwards
2001-11-19 12:17       ` Keith Seitz
2001-11-19 12:06     ` Grant Edwards
2001-11-19 12:00   ` Keith Seitz

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=Pine.GSO.4.33.0111191249421.16197-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=grante@visi.com \
    --cc=insight@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).