From: Christophe-Marie Duquesne <chm.duquesne@gmail.com>
To: mweglicki8208 <mweglicki@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB steping into STL Headers.
Date: Fri, 12 Feb 2010 10:43:00 -0000 [thread overview]
Message-ID: <8ccc3511002120243t629557f3n188996f224c76000@mail.gmail.com> (raw)
In-Reply-To: <27560876.post@talk.nabble.com>
On Fri, Feb 12, 2010 at 10:32 AM, mweglicki8208 <mweglicki@gmail.com> wrote:
>
> So could explain how should i give my compiler information not to pass those
> inline calls information? Is it possible?
>
> It's quite confusing, getting through simple line, with so many GDB "calls".
>
> 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 irritating
> to answer same questions all the time...But at least please point me into
> right direction.
>
> Thanks for help.
>
>
>
>
> Jim Ingham wrote:
>>
>> Hey, cool. Our gdb's been doing that for a couple of years now, glad 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? Then next would also step
>>>> in, since gdb doesn't see inlined functions as new frames.
>>>
>>> Maybe your GDB doesn't :-P GDB 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 — 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
--
Christophe-Marie Duquesne
06 84 14 26 82 - mobile
04 76 57 48 06 - g-scop
04 97 04 27 33 - amadeus
prev parent reply other threads:[~2010-02-12 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 17:38 mweglicki8208
2010-02-11 2:26 ` Hui Zhu
2010-02-11 6:22 ` mweglicki8208
2010-02-11 9:28 ` Obtaining number of children of a dynamic varobj Elmenthaler, Jens
2010-02-11 17:23 ` Vladimir Prus
2010-02-11 17:56 ` GDB steping into STL Headers Tom Tromey
2010-02-11 19:03 ` Jim Ingham
2010-02-11 19:09 ` Daniel Jacobowitz
2010-02-11 19:12 ` Jim Ingham
2010-02-12 9:32 ` mweglicki8208
2010-02-12 10:43 ` Christophe-Marie Duquesne [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ccc3511002120243t629557f3n188996f224c76000@mail.gmail.com \
--to=chm.duquesne@gmail.com \
--cc=gdb@sourceware.org \
--cc=mweglicki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox