Runs on PPC, crashes on Intel
Runs on PPC, crashes on Intel
- Subject: Runs on PPC, crashes on Intel
- From: "Robert J. Lang" <email@hidden>
- Date: Fri, 24 Feb 2006 14:36:49 -0800
- Thread-topic: Runs on PPC, crashes on Intel
Hi,
I'm building a UB app based on wxWidgets, using Xcode 2.2 on OS X 10.4.5,
using the 10.4u SDK. The code compiles and runs on PPC just fine (also on
linux and WinXP, but that's probably not relevant here). The UB runs
properly on Intel Mac under Rosetta, but crashes, repeatably, running native
on Intel.
A difficulty in tracking this down is that I don't own an Intel Mac (sigh),
but I have a tester that does, who sends me the crash log. Here's the top of
one:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xfffffff4
Thread 0 Crashed:
0 libstdc++.6.dylib 0x90b23a21 std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::assign(char const*, unsigned
long) + 39
1 libstdc++.6.dylib 0x90b20089 std::basic_stringbuf<char,
std::char_traits<char>, std::allocator<char> >::str(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&) + 37
2 com.langorigami.TreeMaker 0x0000d280 tmTree::CleanupAfterEdit() + 68
3 com.langorigami.TreeMaker 0x00012f7e tmTree::MakeTreeBlank() + 154
4 com.langorigami.TreeMaker 0x00048973 tmwxDoc::tmwxDoc[in-charge]() +
119
So, it's crashing in libstdc++. The offending line of source code in my
routine (in tmTree::CleanupAfterEdit()) is:
extern stringstream dbgPreCleanupStr;
dbgPreCleanupStr.str("");
which looks like a perfectly innocuous, legal call (and indeed, if I build a
small test app that includes this call, it compiles and runs on Intel).
(stringstream dbgPreCleanupStr is a static variable that was initialized
with the default ctor elsewhere.)
And, as I said, the app runs fine on PPC.
I realize that by far the most direct solution would be to debug natively on
Intel; but lacking a MacBook, since I am relying for the moment on the
generosity of my Intel-owning testers, can anyone suggest any avenues of
exploration? Or does this particular crash ring any bells?
Thanks in advance,
Robert
_______________________________________________
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