Re: linux programming
- From: "David Schwartz" <davids@xxxxxxxxxxxxx>
- Date: 31 Aug 2006 13:10:02 -0700
Martin Jørgensen wrote:
Are you sure? Or has it maybe started stepping through the macroes in
the standard template library? No way to avoid that, that I know of...
Or into the library itself.
Oh, perhaps thats what it did then... I'm relatively new with linux
programming. I just saw that the title frame window changed it's file
name location to something inside
...linuxSrc/gcc-4.1.1-obj/i686-pc-linux-gnu/libstdc++-v3/include/bits/basic_string.h:283:9689:beg:0xb74b4176
- whatever that means....
And then I see strange and weird code like this:
template<typename _CharT, typename _Traits, typename _Alloc>
basic_string<_CharT, _Traits, _Alloc>::
basic_string(const basic_String& __str)
: _M_dataplus(__str._M_rep()->_M_grab(_Alloc(__str.get_allocator()),
__str.get_allocator()),
__str.get_allocator())
{}
etc.etc.etc.... And I find *that* really confusing... Is is just
stepping into the macros in the STL?
No, but it's stepping into the code that your code called. This is a
template, not a macro. Though they have similar effects, a key
difference is that with a template, the template code is your actual
code. Whereas, with a macro, it builds code into your code that runs.
What do you think the debugger should do if you call a library
function? Why shouldn't it step into it? What would the alternative be?
DS
.
- References:
- linux programming
- From: Martin Jørgensen
- Re: linux programming
- From: Joe Pfeiffer
- Re: linux programming
- From: Martin Jørgensen
- linux programming
- Prev by Date: Re: linux programming
- Previous by thread: Re: linux programming
- Next by thread: app developement
- Index(es):
Relevant Pages
|