From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7104 invoked by alias); 29 Mar 2004 08:48:13 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6982 invoked from network); 29 Mar 2004 08:48:10 -0000 Received: from unknown (HELO miranda.se.axis.com) (193.13.178.2) by sources.redhat.com with SMTP; 29 Mar 2004 08:48:10 -0000 Received: from axis.com (ironmaiden.se.axis.com [10.13.8.120]) by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id i2T8laUm032424; Mon, 29 Mar 2004 10:47:36 +0200 Message-ID: <4067E2A8.7040307@axis.com> Date: Mon, 29 Mar 2004 08:48:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb-patches@sources.redhat.com Subject: Re: Next over function and breakpoint setting References: <40572066.2020304@axis.com> <20040327055037.GA9418@nevyn.them.org> In-Reply-To: <20040327055037.GA9418@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00712.txt.bz2 Daniel Jacobowitz wrote: > > "The next line of code" is a very iffy concept. GDB doesn't analyze a > line to figure out what it does, or where it might transfer control > to... while possible, that would be a very different approach to > debugging. So the only way we have to implement next is to step and > see where we end up - and if we don't like it, go until we're somewhere > else. I guess I wasn't really asking a question - I was just confused by the way it was implemented since it wasn't what I had expected. Anyhow, thanks for clearing that up. -- Orjan Friberg Axis Communications