From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21702 invoked by alias); 17 Dec 2001 15:09:03 -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 20555 invoked from network); 17 Dec 2001 15:07:42 -0000 Received: from unknown (HELO quasar.osc.edu) (192.148.249.15) by sources.redhat.com with SMTP; 17 Dec 2001 15:07:42 -0000 Received: (from pw@localhost) by quasar.osc.edu (8.11.4/8.11.4) id fBHF9ru04879; Mon, 17 Dec 2001 10:09:53 -0500 Date: Mon, 17 Dec 2001 07:09:00 -0000 From: Pete Wyckoff To: gdb@sources.redhat.com Subject: step_range_(start|end) Message-ID: <20011217100953.C4370@osc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-SW-Source: 2001-12/txt/msg00151.txt.bz2 I'm trying to shape up my remote backend to gdb so that it's happy with things that 5.1 is sending it. One of these is, for example, "e1,1". Although gdb is content to accept an error from the remote and issue "s" (step) instead, I thought it would be nice to make "e" work too. My confusion, though, is about the two parameters. There's no entry in the documentation for 'e', and I find it passing two variables: step_range_start step_range_end These are defined as CORE_ADDR, and filled with calls like find_pc_line_pc_range (stop_pc, &step_range_start, &step_range_end); which makes sense to me, but then I see other places like: step_range_start = step_range_end = 1; which sure don't sound like CORE_ADDRs. What should I do with an 'e' command in the remote backend (other than ignore it)? -- Pete