public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Paul Whitfield <paulw@microsol.iinet.net.au>
To: bdm-devel@lists.sourceforge.net
Cc: insight@sources.redhat.com
Subject: Re: [Bdm-devel] RE: Problems using Insight/GDB for Coldfire
Date: Tue, 07 Oct 2003 01:19:00 -0000	[thread overview]
Message-ID: <3F82141F.9080506@microsol.iinet.net.au> (raw)
In-Reply-To: <DAE2122934E1F749B243384F5E6DF52421A0F4@corvus.de.3soft>

Dörr, Dirk wrote:

> Paul Whitfield wrote:
> 
> 
> 
>>(gdb) tk gdb_target_has_execution
>>0
> 
> 
>>(gdb) tk set ::gdb_running
>>0

I took the code and added the line

    inferior_ptid = pid_to_ptid (42000);	/* Make run command think we 
are busy... */

This now enables all the buttons.

But if I attempt to load a new file, then get the following
sequence

Insight tells me that a debugging session is in progress and do
I want to end it.

Then when I attempt to load the file I get an error
(If I load the file from the console by typing "load file.elf" it
works without error).

After this the buttons are confused again.
Checking the settings again

gdb_target_has_execution is 1,::gdb_running is still 0.

Looks like I have not quite found the right spot to
set the pid!

Also if I load my program by scripts and start everything
running I have the same problem when I hit the first
breakpoint, i.e. insight thinks that the target
is not running again.



Regards

Paul





  reply	other threads:[~2003-10-07  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 12:31 "Dörr, Dirk"
2003-10-07  1:19 ` Paul Whitfield [this message]
2003-10-07 16:28   ` Keith Seitz
  -- strict thread matches above, loose matches on Subject: below --
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

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=3F82141F.9080506@microsol.iinet.net.au \
    --to=paulw@microsol.iinet.net.au \
    --cc=bdm-devel@lists.sourceforge.net \
    --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).