public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Paul Whitfield <paulw@microsol.iinet.net.au>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>,
	bdm-devel@lists.sourceforge.net
Subject: Re: [Bdm-devel] RE: Problems using Insight/GDB for Coldfire
Date: Fri, 03 Oct 2003 03:34:00 -0000	[thread overview]
Message-ID: <1065152253.1588.103.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <3F7CCECD.3010004@microsol.iinet.net.au>

On Thu, 2003-10-02 at 18:20, Paul Whitfield wrote:
> (gdb) target bdm /dev/bdmcf0
> Remote bdm connected to /dev/bdmcf0
>   Coldfire debug module version is 1 (5307/5407(e))
> 
> (gdb) tk gdb_target_has_execution
> 0

This is a problem. This indicates a problem with the target backend.
It's not setting the pid/ptid when the target is attached. See
src/gdb/gdbtk/generic/gdbtk-cmds.c:gdb_target_has_execution_command.

Normally, one of the target vector commands will set ptid (or pid for
older versions of gdb) to non-zero -- typically 42000 or some other
"significant" number.

If you have the source code for the backend, check that something in the
target vector sets the ptid on attach. (See, for example, monitor_open
in monitor.c, which sets "inferior_pid = pid_to_ptid (42000);".

Keith


  reply	other threads:[~2003-10-03  3:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  6:50 "Dörr, Dirk"
2003-10-01  7:24 ` [Bdm-devel] " Chris Johns
2003-10-01  7:33 ` Paul Whitfield
2003-10-02 16:01   ` Keith Seitz
2003-10-03  1:31     ` Paul Whitfield
2003-10-03  3:34       ` Keith Seitz [this message]
2003-10-06 12:31 "Dörr, Dirk"
2003-10-07  1:19 ` Paul Whitfield
2003-10-07 16:28   ` 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=1065152253.1588.103.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=bdm-devel@lists.sourceforge.net \
    --cc=insight@sources.redhat.com \
    --cc=paulw@microsol.iinet.net.au \
    /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).