From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30524 invoked by alias); 19 Dec 2001 17:00:13 -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 30263 invoked from network); 19 Dec 2001 16:58:54 -0000 Received: from unknown (HELO mail.pathwayconnect.com) (209.91.95.13) by sources.redhat.com with SMTP; 19 Dec 2001 16:58:54 -0000 Received: (qmail 32119 invoked from network); 19 Dec 2001 16:58:51 -0000 Received: from unknown (HELO dazed) (192.168.0.149) by 0 with SMTP; 19 Dec 2001 16:58:51 -0000 Received: from dazed ([127.0.0.1] helo=there ident=sjackman) by dazed with smtp (Exim 3.32 #1 (Debian)) id 16Gk2s-0007Jk-00 for ; Wed, 19 Dec 2001 09:58:18 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Shaun Jackman Organization: Pathway Connectivity To: gdb@sources.redhat.com Subject: Can't connect to remote target in a confused state Date: Wed, 19 Dec 2001 09:00:00 -0000 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: X-SW-Source: 2001-12/txt/msg00168.txt.bz2 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