From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10329 invoked by alias); 3 Jan 2007 19:59:24 -0000 Received: (qmail 10320 invoked by uid 22791); 3 Jan 2007 19:59:23 -0000 X-Spam-Check-By: sourceware.org Received: from tmpnat1.honeywell.com (HELO az18cn848.global.ds.honeywell.com) (199.64.0.252) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 03 Jan 2007 19:59:17 +0000 Received: from AZ18EV808.global.ds.honeywell.com ([131.127.167.102]) by az18cn848.global.ds.honeywell.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 3 Jan 2007 12:59:15 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: gdb very slow during 'step into' Date: Wed, 03 Jan 2007 19:59:00 -0000 Message-ID: In-Reply-To: From: "Smith, Stephen \(SWCOE\)" To: "Jim Blandy" , "dodji Seketeli" Cc: 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: 2007-01/txt/msg00037.txt.bz2 Sounds good, but I am experiencing the same problem. The trouble is that on my platform, neither symbol is defined (I am running on an embedded platform that does not have glibc ported to it.) What should be the generic fix? -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf Of Jim Blandy Sent: Wednesday, January 03, 2007 12:52 PM To: dodji Seketeli Cc: gdb@sourceware.org Subject: Re: gdb very slow during 'step into' "dodji Seketeli" writes: >> If you set the environment variable LD_BIND_NOW to a non-empty value >> before running your program (use GDB's 'set env' command), does that >> eliminate the slow steps? > > Wow, yes. It does eliminate the problem. Thank you !. I'm glad that helped! But setting LD_BIND_NOW is just a workaround; GDB ought to work properly without that. Could you apply the following patch to GDB and see if it makes the problem go away, even with LD_BIND_NOW left unset? (Tested without regressions on Fedora Core 6 IA-32. I haven't been able to reproduce the problem myself, so I'm just guessing that this is the patch.)