From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 854 invoked by alias); 21 May 2004 15:06:37 -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 643 invoked from network); 21 May 2004 15:06:29 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 21 May 2004 15:06:29 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i4LF6TGI002346 for ; Fri, 21 May 2004 11:06:29 -0400 Received: from localhost.redhat.com (dhcp64-184.boston.redhat.com [172.16.64.184]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i4LF6Q016181; Fri, 21 May 2004 11:06:26 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id A268D2B9D; Fri, 21 May 2004 11:06:23 -0400 (EDT) Message-ID: <40AE1AEF.50201@gnu.org> Date: Fri, 21 May 2004 15:06:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Jon Beniston Cc: "'Daniel Jacobowitz'" , gdb@sources.redhat.com Subject: Re: Remote/simulator differences References: <000f01c43de6$22bf6ec0$04bda8c0@srce> In-Reply-To: <000f01c43de6$22bf6ec0$04bda8c0@srce> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00146.txt.bz2 >>>What's causing it to think that the program has already >> >>> been started? >> >>>> > Is it possible that something in the remote stub is causing >> >>> this? Any >> >>>> > insight would be appreciated. I'm using GDB 6.0. >> >>> >>> For remote, the appropriate command is "continue", or >>> sometimes "jump". >>> It depends on your particular target and monitor. > > > Okay. I have hacked eclipse to take this into account. It works, but I > guess I was hoping for something a little cleaner (at least from > eclipse's perspective). Yes. GDB is very inconsistent when it comes to attaching / starting a target. We [gdb] need to be willing to first define/fix the behavior and second conduct a pr exercise explaining why things are changing to our users. Andrew