This came out a lot along with some other warnings

==26493== warning: Valgrind's pthread_attr_setschedparam does nothing
==26493==          (scheduling not changeable)
==26493==          your program may misbehave as a result
==26493== warning: Valgrind's pthread_attr_destroy does nothing
==26493==          your program may misbehave as a result
==26493== warning: Valgrind's pthread_cond_destroy is incomplete
==26493==          (it doesn't check if the cond is waited on)
==26493==          your program may misbehave as a result


This is the uninterrupted final death throws. Lots of things about
"the impossible occuring".  



==26493== 
==26493== Thread 3:
==26493== Invalid read of size 1
==26493==    at 0x1B9044C8: strlen (mac_replace_strmem.c:189)
==26493==    by 0x1C56CC37: giop_send_buffer_append_string (in /usr/lib/libORBit                               -2.so.0.0.0)
==26493==    by 0x1C579E9C: ORBit_marshal_value (in /usr/lib/libORBit-2.so.0.0.0                               )
==26493==    by 0x1C570ECD: (within /usr/lib/libORBit-2.so.0.0.0)
==26493==  Address 0x501E0E54 is not stack'd, malloc'd or (recently) free'd
==26493== 
==26493== Thread 3:
==26493== Jump to the invalid address stated on the next line
==26493==    at 0x0: ???
==26493==  Address 0x0 is not stack'd, malloc'd or (recently) free'd

valgrind: the `impossible' happened:
   VG_TRC_INNER_FASTMISS: missing tt_fast entry
Basic block ctr is approximately 523100000
==26493==    at 0xB0031A1D: vgPlain_core_panic (vg_mylibc.c:1156)
==26493==    by 0xB0031A1C: panic (vg_mylibc.c:1152)
==26493==    by 0xB0031A3D: vgPlain_core_panic (vg_mylibc.c:1157)
==26493==    by 0xB000DD44: do_scheduler (vg_scheduler.c:1034)

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==26493==    at 0x1C78D322: select (in /lib/libc-2.3.4.so)
==26493==    by 0x1D4A0BD7: ???
==26493==    by 0x1D4A381F: ???
==26493==    by 0x1D471025: ???

Thread 2: status = WaitCV, associated_mx = 0x1CC13388, associated_cv = 0x1CC3577                               0
==26493==    at 0x1C62E4BF: pthread_cond_wait (vg_libpthread.c:1452)
==26493==    by 0x1C666B46: (within /usr/lib/libglib-2.0.so.0.400.8)
==26493==    by 0x1C69AF0A: (within /usr/lib/libglib-2.0.so.0.400.8)
==26493==    by 0x1C698A4A: (within /usr/lib/libglib-2.0.so.0.400.8)

Thread 3: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==26493==    at 0x1C3293A0: (within /usr/lib/libgstreamer-0.8.so.1.4.0)

Thread 4: status = WaitCV, associated_mx = 0x1CB8A030, associated_cv = 0x1CC35FF                               0
==26493==    at 0x1C62E6F0: pthread_cond_timedwait (vg_libpthread.c:1488)

Thread 5: status = WaitCV, associated_mx = 0x1CB8A0C0, associated_cv = 0x1CC358C                               8
==26493==    at 0x1C62E6F0: pthread_cond_timedwait (vg_libpthread.c:1488)

Thread 6: status = WaitSys, associated_mx = 0x0, associated_cv = 0x0
==26493==    at 0x1C78B0F8: poll (in /lib/libc-2.3.4.so)

Thread 7: status = WaitCV, associated_mx = 0x1CB00C18, associated_cv = 0x1CD4337                               0
==26493==    at 0x1C62E4BF: pthread_cond_wait (vg_libpthread.c:1452)

Thread 8: status = WaitCV, associated_mx = 0x1CB287C8, associated_cv = 0x1CCFCEC                               8
==26493==    at 0x1C62E4BF: pthread_cond_wait (vg_libpthread.c:1452)


Note: see also the FAQ.txt in the source distribution.
It contains workarounds to several common problems.

If that doesn't help, please report this bug to: valgrind.kde.org

In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using.  Thanks.

