From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31974 invoked by alias); 18 Mar 2010 21:17:09 -0000 Received: (qmail 31965 invoked by uid 22791); 18 Mar 2010 21:17:08 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Mar 2010 21:17:04 +0000 Received: (qmail 6848 invoked from network); 18 Mar 2010 21:17:03 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Mar 2010 21:17:03 -0000 From: Pedro Alves To: Michael Snyder Subject: Re: Getting pissed off by gdb. Please help with stepping in. Date: Thu, 18 Mar 2010 21:17:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-19-generic; KDE/4.3.2; x86_64; ; ) Cc: Doug Evans , Mark Kettenis , "eliz@gnu.org" , "gdb@sourceware.org" , "temp@sourceboost.com" References: <11611.203.63.255.139.1268879984.squirrel@webmail5.pair.com> <4BA29262.1080509@vmware.com> In-Reply-To: <4BA29262.1080509@vmware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003182116.59273.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-03/txt/msg00155.txt.bz2 On Thursday 18 March 2010 20:51:46, Michael Snyder wrote: > Am I the only one who remembers that gdb used to have the behavior that > is being discussed, and it was deliberately changed to behave the way it > does today? > > My admittedly fallable memory cells are telling me that it was Fernando > Nasser who championed the change, which means that it would have been > at least five years ago. > > If I am right, the argument then was that the new behavior (what gdb > has today) was closer to what users would expect. Perhaps it was "step-mode" instead (or changing it's default)? You mentioned a command/setting for what you thought remembered, but what we're discussing doesn't have a knob... (gdb) help set step-mode Set mode of the step operation. When set, doing a step over a function without debug line information will stop at the first instruction of that function. Otherwise, the function is skipped and the step command stops at a different source line. -- Pedro Alves