From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3381 invoked by alias); 18 Mar 2010 22:44:46 -0000 Received: (qmail 3371 invoked by uid 22791); 18 Mar 2010 22:44:45 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from wbm9.pair.net (HELO wbm9.pair.net) (66.39.3.87) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Mar 2010 22:44:40 +0000 Received: by wbm9.pair.net (Postfix, from userid 65534) id 7FE458889F; Thu, 18 Mar 2010 18:44:38 -0400 (EDT) Received: from 203.63.255.139 ([203.63.255.139]) (SquirrelMail authenticated user temp@sourceboost.com) by webmail9.pair.com with HTTP; Thu, 18 Mar 2010 18:44:38 -0400 (EDT) Message-ID: <2374.203.63.255.139.1268952278.squirrel@webmail9.pair.com> Date: Thu, 18 Mar 2010 22:44:00 -0000 Subject: Re: Getting pissed off by gdb. Please help with stepping in. From: temp@sourceboost.com To: gdb@sourceware.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit References: <11611.203.63.255.139.1268879984.squirrel@webmail5.pair.com> In-Reply-To: <11611.203.63.255.139.1268879984.squirrel@webmail5.pair.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/msg00157.txt.bz2 Thanks for all the replies. I see different people have reasons for different behaviour. If it helps let me tell what I'd like to see. If I'm inside bar than when I do finish I want to get out of bar and remain on 'foo( bar() )'. If I keep hitting next or step I should eventually get out of bar and remain on 'foo( bar() )'. Rationale: when I'm done with bar debugging I want to have a choice: either to be able to go into foo or, if I'm not interested in foo, step over it. If I'm on the line 'foo( bar() )' I would like to have 2 options (this applies to both gdb and microsoft debugggers). Either step into bar (existing behaviour) or step over all calls used in arguments and step right into foo (this isn't supported, isn't it?). Rationale: if call to foo looks like 'foo( bar1(), bar2(), bar2(), bar4() )' and I'm not interested in all these bars I need an option to that will be most productive for this case: go directly inside foo. Pavel