From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12321 invoked by alias); 12 Feb 2010 10:43:45 -0000 Received: (qmail 12308 invoked by uid 22791); 12 Feb 2010 10:43:43 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f223.google.com (HELO mail-ew0-f223.google.com) (209.85.219.223) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Feb 2010 10:43:38 +0000 Received: by ewy23 with SMTP id 23so104368ewy.4 for ; Fri, 12 Feb 2010 02:43:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.88.205 with SMTP id a55mr686788wef.122.1265971415124; Fri, 12 Feb 2010 02:43:35 -0800 (PST) In-Reply-To: <27560876.post@talk.nabble.com> References: <27535106.post@talk.nabble.com> <27542787.post@talk.nabble.com> <1CF86F7D-0B47-47D7-A6E2-24853D50653D@apple.com> <20100211190921.GA20235@caradoc.them.org> <35CF0705-79F2-4AA2-B863-62D1294E1F1C@apple.com> <27560876.post@talk.nabble.com> From: Christophe-Marie Duquesne Date: Fri, 12 Feb 2010 10:43:00 -0000 Message-ID: <8ccc3511002120243t629557f3n188996f224c76000@mail.gmail.com> Subject: Re: GDB steping into STL Headers. To: mweglicki8208 Cc: gdb@sourceware.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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-02/txt/msg00088.txt.bz2 On Fri, Feb 12, 2010 at 10:32 AM, mweglicki8208 wrote: > > So could explain how should i give my compiler information not to pass th= ose > inline calls information? Is it possible? > > It's quite confusing, getting through simple line, with so many GDB "call= s". > > I'm using older version of gcc actually and i can't change it...( 3.4.5 ). > > I understand that I'm quite new to the subject, and it has to be irritati= ng > to answer same questions all the time...But at least please point me into > right direction. > > Thanks for help. > > > > > Jim Ingham wrote: >> >> Hey, cool. =C2=A0Our gdb's been doing that for a couple of years now, gl= ad you >> caught up :-D >> >> Jim >> >> On Feb 11, 2010, at 11:09 AM, Daniel Jacobowitz wrote: >> >>> On Thu, Feb 11, 2010 at 11:03:08AM -0800, Jim Ingham wrote: >>>> It sounds like the STL code got inlined? =C2=A0Then next would also st= ep >>>> in, since gdb doesn't see inlined functions as new frames. >>> >>> Maybe your GDB doesn't :-P =C2=A0GDB 7.0 does support inlined functions= - >>> if your compiler outputs correct DWARF, at least. >>> >>> -- >>> Daniel Jacobowitz >>> CodeSourcery >> >> >> > > Please read the manual: http://sourceware.org/gdb/current/onlinedocs/gdb/Inline-Functions.html "For gdb to support inlined functions, the compiler must record information about inlining in the debug information =E2=80=94 gcc using the dwarf 2 format does this, and several other compilers do also. gdb only supports inlined functions when using dwarf 2. Versions of gcc before 4.1 do not emit two required attributes (`DW_AT_call_file' and `DW_AT_call_line'); gdb does not display inlined function calls with earlier versions of gcc. It instead displays the arguments and local variables of inlined functions as local variables in the caller. " I guess you have two solutions: 1 ) Update your compiler to gcc-4.4.3 2 ) Tell your compiler *not* to inline function, using -fno-inline --=20 Christophe-Marie Duquesne 06 84 14 26 82 - mobile 04 76 57 48 06 - g-scop 04 97 04 27 33 - amadeus