Re: Libstdc++ problems
Re: Libstdc++ problems
- Subject: Re: Libstdc++ problems
- From: Mike Linden <email@hidden>
- Date: Mon, 26 Feb 2007 16:00:20 -0500
You are correct in your discussion and I understand what you are saying.
Yes, I'm not trying to change any data the c_str() is pointing to and
yes I agree there are no guarantees as to where the data is located.
My only reason for stating my examination was in hopes of
'triggering' someone's memory as to what might be causing the things
that I'm seeing.
The fact is c_str() does not work for me. I don't know why. Since
this code (framework) compiles other platforms and CodeWarrior, I can
only assume that I'm missing something in the Xcode setup.
Below is the debugger showing were it went for the exception.
My guess is whatever is causing the problem with c_str() is also
causing this problem.
My known 'good' execution is that .data() returns the const char*
pointer correctly.
I don't understand this either since both are returning the same data as was
pointed out.
Is it possible the some type of casting is needed, that is different from
normal C++ standards?
This is Xcode 2.4.1 compiling in 10.4.7.
Thanks for your help.
#0 0x9004802c in kill
#1 0x9012dfb4 in abort
#2 0x0024b63c in std::dthandler
#3 0x0024b5d0 in std::terminate
#4 0x00248654 in ExPPC_ThrowHandler
#5 0x00248078 in __throw_vec
#6 0x00248408 in __throw
#7 0x00280af0 in std::string::replace
#8 0x0028b104 in std::basic_string<char, std::char_traits<char>,
std::allocator<char> >::basic_string
#9 0x0028a548 in std::string::substr
#10 0x0105cd84 in XPDBSearch::_parseReadBufferAdv at XPDBSearch.cpp:2533
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden