From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32455 invoked by alias); 11 Aug 2003 15:15:14 -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 32447 invoked from network); 11 Aug 2003 15:15:13 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 11 Aug 2003 15:15:13 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id LAA30283 for ; Mon, 11 Aug 2003 11:13:47 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id LAA04316 for ; Mon, 11 Aug 2003 11:15:12 -0400 Message-ID: <078701c3601b$5775b060$0202040a@catdog> From: "Kris Warkentin" To: "Gdb@Sources.Redhat.Com" Subject: Stepping over shared library call Date: Mon, 11 Aug 2003 15:15:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-08/txt/msg00129.txt.bz2 When I do a 'step' on a function that is in a shared library (such as printf), what mechanisms/criteria does gdb use to determine whether to single step all the way through it or just to stop on the next line of code? I've observed that if the symbols are loaded for libc, gdb steps all the way through the call but otherwise skips over it. Is this expected behaviour? I believe it is because one could have a situation where there is some debug info in a shared lib (or a non-debug shared lib calls into a debug one). If this were the case, you'd want gdb to step until it finds some debug information right? Basically I'm planning on telling customers, "Use 'next' if you want to go to the next line and only use step if you want to step into the call." This wouldn't be an issue if everyone just did local debugging but when you're debugging a remote system, single stepping through a shared library call can take a hellishly long time. cheers, Kris