"Robert A. Schmied" <ras@xxxxxxx> writes: > built gcc-4.4.6 on older solaris 10 sparc using the shipped gcc at /usr/sfw/bin > % gcc --version > gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) > > --enable-languages="c,c++" > > > i see in each of the testsuite dirs listed below a core dump, in all cases the > cause is a SIGABRT: Abort > ./gcc/testsuite/gcc > ./gcc/testsuite/g++ > ./sparc-sun-solaris2.10/libgomp/testsuite > ./sparc-sun-solaris2.10/libstdc++-v3/testsuite > > is this a cause for concern? i wasn't able to figure out a way to id > which test is causing the core, (clues welcome). I would not worry about a core dump appearing in those testsuite directories. There are many possible causes for that. Ian
