From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7828 invoked by alias); 19 Dec 2001 19:46:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7807 invoked from network); 19 Dec 2001 19:46:58 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 19 Dec 2001 19:46:58 -0000 Received: from rtl.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id LAA07261; Wed, 19 Dec 2001 11:46:54 -0800 (PST) Received: (from ezannoni@localhost) by rtl.cygnus.com (8.11.2/8.11.0) id fBJIxjb02574; Wed, 19 Dec 2001 13:59:45 -0500 X-Authentication-Warning: localhost.localdomain: ezannoni set sender to ezannoni@cygnus.com using -f From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15392.58272.880164.15301@localhost.localdomain> Date: Wed, 19 Dec 2001 11:46:00 -0000 To: Shaun Jackman Cc: gdb@sources.redhat.com Subject: Re: Can't connect to remote target in a confused state In-Reply-To: References: X-Mailer: VM 7.00 under Emacs 20.7.1 X-SW-Source: 2001-12/txt/msg00174.txt.bz2 Shaun, this is a known problem with arm. I submitted a patch some time back, and haven't committed it yet. Some minor cleanup is needed. Try it anyway and see if it works for you: http://sources.redhat.com/ml/gdb-patches/2001-11/msg00396.html Elena Shaun Jackman writes: > 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