[gst-devel] valgrind

[Joshua N Pritikin]

On Sat, Jan 04, 2003 at 09:46:37PM -0800, Erik Walthinsen wrote:
> On Sun, 5 Jan 2003, Joshua N Pritikin wrote:
> > disInstr: unhandled 2-byte opcode 0xC7
> > This _might_ be the result of executing an MMX, SSE, SSE2 or 3DNow!
> > instruction.  Valgrind does not currently support such instructions.  Sorry.
> > Illegal instruction
> >
> > Any clue what is causing this?  i configured with:
> 
> Somewhere something is doing an 'emms' (0x0f 0xc7) anyway.  Can valgrind
> and gdb cooperate and give you a backtrace when that happens?

Uh .. yah:

RUNNING pipeline
disInstr: unhandled 2-byte opcode 0xC7
This _might_ be the result of executing an MMX, SSE, SSE2 or 3DNow!
instruction.  Valgrind does not currently support such instructions.  Sorry.
disInstr: unhandled 2-byte opcode 0x75
This _might_ be the result of executing an MMX, SSE, SSE2 or 3DNow!
instruction.  Valgrind does not currently support such instructions.  Sorry.
disInstr: unhandled opcode 0xF5 then 0x89

valgrind: the `impossible' happened:
   unhandled x86 opcode
Basic block ctr is approximately 32450000

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==25236==    at 0x402321FB: gst_trash_stack_pop (gsttrashstack.h:100)
==25236==    by 0x402324D0: gst_mem_chunk_alloc (gstmemchunk.c:174)
==25236==    by 0x4023251C: gst_mem_chunk_alloc0 (gstmemchunk.c:199)
==25236==    by 0x40224A51: gst_buffer_new (gstbuffer.c:175)

Cutting the asm stuff in gsttrashstack .. more reports to follow.

-- 
Victory to the Divine Mother!!         after all,
  http://sahajayoga.org                  http://why-compete.org