libgmalloc bug
libgmalloc bug
- Subject: libgmalloc bug
- From: Salvatore Domenick Desiano <email@hidden>
- Date: Mon, 5 Mar 2007 15:47:53 -0500 (EST)
- Resent-date: Mon, 5 Mar 2007 15:57:04 -0500 (EST)
- Resent-from: THIS MAIL HAS NO ROLE <email@hidden>
- Resent-message-id: <email@hidden>
- Resent-subject: libgmalloc bug
- Resent-to: email@hidden
I'm not sure if this is a libgmalloc bug, a gcc bug, or a iostream bug,
but I just spent 20 hours boiling a crash in opencv down to ten lines of
code. Can somebody else on a MacBook Pro run the following and see if
they get a seg fault? Input from a PPC based processor also welcome.
So frustrating!
Is this the right Apple mailing list? If this is a bug, where would I
report it?
Thanks!
-- Sal
smile.
cat > bug.cpp
#include <iostream>
void test ()
{
for(unsigned i = 1; i < 3; ++i )
{
std::cout << "HELLO";
}
}
int main (int argn, char * argv)
{
test();
return 0;
}
^D
g++ -Wall -fomit-frame-pointer -O1 -o bug bug.cpp
setenv DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib
./bug
--------------
Salvatore Domenick Desiano
Doctoral Candidate
Robotics Institute
Carnegie Mellon University
_______________________________________________
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