From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20405 invoked by alias); 11 Feb 2010 17:56:18 -0000 Received: (qmail 20396 invoked by uid 22791); 11 Feb 2010 17:56:17 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Feb 2010 17:56:13 +0000 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o1BHuB50012376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 11 Feb 2010 12:56:11 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o1BHuAE2021063; Thu, 11 Feb 2010 12:56:10 -0500 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id o1BHu9cf017564; Thu, 11 Feb 2010 12:56:10 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 481C9378261; Thu, 11 Feb 2010 10:56:09 -0700 (MST) From: Tom Tromey To: mweglicki8208 Cc: gdb@sourceware.org Subject: Re: GDB steping into STL Headers. References: <27535106.post@talk.nabble.com> <27542787.post@talk.nabble.com> Reply-To: tromey@redhat.com Date: Thu, 11 Feb 2010 17:56:00 -0000 In-Reply-To: <27542787.post@talk.nabble.com> (mweglicki@gmail.com's message of "Wed, 10 Feb 2010 22:21:56 -0800 (PST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-02/txt/msg00068.txt.bz2 >>>>> ">" == mweglicki8208 writes: [ "next" ] >> Of course I tried next. But in this respect it behaves the same as "step". >> Maybe there is something wrong with my gdb configuration.... That is surprising, since "next" should step over calls. Anyway, no, there is no way in gdb to disable stepping into certain calls. This feature is requested fairly frequently, but so far nobody has worked on implementing it. This is also http://sourceware.org/bugzilla/show_bug.cgi?id=8287 FWIW I think this would be a good feature to have. Tom