From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-7172-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 6839 invoked by alias); 19 Dec 2001 17:21:34 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 6362 invoked from network); 19 Dec 2001 17:20:18 -0000
Received: from unknown (HELO mail.pathwayconnect.com) (209.91.95.13)
  by sources.redhat.com with SMTP; 19 Dec 2001 17:20:18 -0000
Received: (qmail 32207 invoked from network); 19 Dec 2001 17:20:15 -0000
Received: from unknown (HELO dazed) (192.168.0.149)
  by 0 with SMTP; 19 Dec 2001 17:20:15 -0000
Received: from dazed
	([127.0.0.1] helo=there ident=sjackman)
	by dazed with smtp (Exim 3.32 #1 (Debian))
	id 16GkNa-0007Kb-00
	for <gdb@sources.redhat.com>; Wed, 19 Dec 2001 10:19:42 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Shaun Jackman <sjackman@pathwayconnect.com>
Organization: Pathway Connectivity
To: gdb@sources.redhat.com
Subject: Re: Can't connect to remote target in a confused state
Date: Wed, 19 Dec 2001 09:21:00 -0000
X-Mailer: KMail [version 1.3.2]
References: <E16Gk2s-0007Jk-00@dazed>
In-Reply-To: <E16Gk2s-0007Jk-00@dazed>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <E16GkNa-0007Kb-00@dazed>
X-SW-Source: 2001-12/txt/msg00169.txt.bz2

I forgot to mention I'm using gdb 5.1 on an i686 host.

Cheers,
Shaun

On December 19, 2001 09:58, Shaun Jackman wrote:
> Occasionally my target (arm-elf) may lose its brain due to a program error,
> or what have you. Regardless, I'd still like to be able to attach to it
> with gdb. I use a JTAG device (BDI2000) and as long as the ARM core isn't
> frozen I should be able to attach. This is the error I'm getting...
>
> (gdb) target remote bdi:2001
> Couldn't establish connection to remote target
> Cannot access memory at address 0xeafffff4
>
> Now, I assume when I attach gdb is trying to figure out what frame/stack
> etc it's in. So one of the frame pointer, or stack pointer, or program
> counter is sitting at 0xeafffff4 and gdb is trying to read the memory
> there. When it can't, it fails. Unfortunately, when this happens I have to
> power-cycle my target and restart gdb to be able to get back to debugging.
>
> Is my analysis correct? Is there some way I can get gdb to attach to the
> target even if it has been left in a "confused" state? My next actions are
> likely going to be to "load" and "run" anyways, so I really don't care that
> it's confused at the moment.
>
> Thanks,
> Shaun