------- Comment #3 from jakub at gcc dot gnu dot org 2005-12-29 10:04 -------
Couldn't reproduce, on neither 4way nor UP box, with various OMP_NUM_THREADS
settings in environment. The valgrind output isn't really helpful, because
when it reaches unhandled insn, all bets are off what happens afterwards and
also because you must have libstdc++ stripped as it isn't showing location
within libstdc++ where it faulted.
You should instead run it under gdb and get a backtrace from it.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25527
