From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16147 invoked by alias); 12 Feb 2002 22:14:27 -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 16011 invoked from network); 12 Feb 2002 22:14:22 -0000 Received: from unknown (HELO toenail.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 12 Feb 2002 22:14:22 -0000 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.11.6/8.11.6) id g1CMELY18115; Tue, 12 Feb 2002 17:14:21 -0500 Date: Tue, 12 Feb 2002 14:14:00 -0000 From: "Frank Ch. Eigler" To: sid@sources.redhat.com Cc: gdb@sources.redhat.com Subject: sid debugger interface extension: step out-of-range packet support Message-ID: <20020212171421.D13536@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-SW-Source: 2002-q1/txt/msg00031.txt.bz2 Hi - 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. This packet makes remote debugging potentially significantly faster, because it can replace a sequence of instruction single-step packets with just one new packet. This finally exercises J.T. Conklin's gdb-side extensions from roughly a year ago. There is a gdb bug that is exposed by this support. If a breakpoint placed on the current instruction, and another one on the next source line, then letting gdb "step" will stop at the next line, but won't let gdb realize that the second breakpoint was hit. (This is because gdb never inserted the breakpoints in gdb/infrun.c's proceed(), being unaware that remote_resume() meant something other than stepi.) This looks like this is a minor problem, but just in case, support for the packet may be forced off from the gdb side and/or from the sid side. - FChE