FWIW, my MacBook Pro gets a segfault running your test program with DYLD_INSERT_LIBRARIES=/usr/lib/libgmalloc.dylib in the environment, too. Dave On Mar 5, 2007, at 12:24 , Salvatore Domenick Desiano wrote:

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.

If this is a problem, I'm not even sure how to go back and fix the OpenCV port, but if it's not, but at least I'll know I'm working on a real problem.

So frustrating!

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 _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev

Thank you for everyone's help. Looks like a confirmed bug, and only on the Pros. Now to figure out what to do with it. -- Sal smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Mon, 5 Mar 2007, Salvatore Domenick Desiano wrote: o Excellent. Thank you. o o -- Sal o smile. o o o -------------- o Salvatore Domenick Desiano o Doctoral Candidate o Robotics Institute o Carnegie Mellon University o o On Mon, 5 Mar 2007, David MacMahon wrote: o o o FWIW, my MacBook Pro gets a segfault running your test program with o o DYLD_INSERT_LIBRARIES=/usr/lib/libgmalloc.dylib in the environment, too. o o o o Dave o o o o On Mar 5, 2007, at 12:24 , Salvatore Domenick Desiano wrote: o o o o > I'm not sure if this is a libgmalloc bug, a gcc bug, or a iostream bug, but o o > I just spent 20 hours boiling a crash in opencv down to ten lines of code. o o > Can somebody else on a MacBook Pro run the following and see if they get a o o > seg fault? Input from a PPC based processor also welcome. o o > o o > If this is a problem, I'm not even sure how to go back and fix the OpenCV o o > port, but if it's not, but at least I'll know I'm working on a real problem. o o > o o > So frustrating! o o > o o > Thanks! o o > o o > -- Sal o o > smile. o o > o o > o o > cat > bug.cpp o o > #include <iostream> o o > o o > void test () o o > { o o > for(unsigned i = 1; i < 3; ++i ) o o > { o o > std::cout << "HELLO"; o o > } o o > } o o > o o > int main (int argn, char * argv) o o > { o o > test(); o o > return 0; o o > } o o > ^D o o > g++ -Wall -fomit-frame-pointer -O1 -o bug bug.cpp o o > setenv DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib o o > ./bug o o > o o > o o > o o > -------------- o o > Salvatore Domenick Desiano o o > Doctoral Candidate o o > Robotics Institute o o > Carnegie Mellon University o o > _______________________________________________ o o > macports-dev mailing list o o > macports-dev@lists.macosforge.org o o > http://lists.macosforge.org/mailman/listinfo/macports-dev o o o o _______________________________________________ o o macports-dev mailing list o o macports-dev@lists.macosforge.org o o http://lists.macosforge.org/mailman/listinfo/macports-dev o o o _______________________________________________ o macports-dev mailing list o macports-dev@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-dev o o