From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24090 invoked by alias); 23 Feb 2002 01:08:19 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 23974 invoked from network); 23 Feb 2002 01:08:16 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 23 Feb 2002 01:08:16 -0000 Received: from redhat.com (notinuse.cygnus.com [205.180.231.12]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id RAA08800; Fri, 22 Feb 2002 17:08:10 -0800 (PST) Message-ID: <3C76E982.972553B6@redhat.com> Date: Fri, 22 Feb 2002 17:08:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Frank Ch. Eigler" CC: cagney@redhat.com, sid@sources.redhat.com, gdb@sources.redhat.com Subject: Re: sid debugger interface extension: step out-of-range packet support References: <20020212171421.D13536@redhat.com> <3C6A0365.4050207@cygnus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q1/txt/msg00036.txt.bz2 "Frank Ch. Eigler" wrote: > > cagney wrote: > > > [...] > > > A small amount of new code in sid/include and sid/component/gdb > > > now allows gdb's "step out-of-range" packet ('e'/'E') to work with > > > all sid-based simulator targets. [...] > > > > [...] I wouldn't rely to much on that current packet and/or > > implementation. A number of issues with it have been pointed out > > with it. Suggest looking through the archives. > > I did. Are you referring to a thread other than this one: > ? I must > admit I don't see the severity of that problem -- it sounds like the > user experience may be a little jarring with multithreaded apps, but > not inconsistent or lossy. If the 'e' packet is going to change gdb's behavior while debugging threads, this needs to be discussed and considered. It may amount to a bug in the specification of the 'e' packet. And in fact, given the behavior that you describe in your first message, the 'e' packet _is_ going to change gdb's behavior while debugging threads.