|
From: Erik de C. L. <eri...@me...> - 2005-09-25 13:30:10
|
Julian Seward wrote:
> Yes. Any access at all below %esp on an x86 is a unconditionally bug
> which could potentially crash your program. If you found such a
> thing and can pin it on gcc, then it's a gcc bug.
OK, I just recompiled the program with gcc-2.95 and the valgrind
error remains. I think that means that the problem is in my code.
The thing that confuses me is the line that valgrind is warning
about is:
retpcm [offset + j] = (buffer [j][pflac->bufferpos]) << shift ;
where all the arrays are on the heap, not the stack.
Anyone have any clues as to how to track this down? Should I look
at the assembler output?
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"Unix and C are the ultimate computer viruses." -- Richard P Gabriel
|