On Fri, Nov 07, 2003 at 04:20:13PM +0100, Bernhard Praschinger wrote:
> Hallo
> 
> > Has anyone tried the current cvs mpeg2enc lately?  I pulled the
> > current cvs on Nov. 4 because I wanted to see for myself how well the
> > new "no B frames please" option worked.  But my copy of mpeg2enc
> > compiled from the source I pulled that day takes a segfault while
> > it's processing the first frame (field?).  Here is a gdb backtrace on
> > the corefile that dumps when it segfaults:
> Just check out the CVS, and compiled it, works well. 
> 
> > The binary was compiled with gcc 2.95.3, and all I did for the test
> > binary was ./configure ; make.  I let it select all it's options.
> > The system is a P4 celeron (properly detected by configure) chip.
> But I use (GCC) 3.3.1
> Maybe there a problems hidden with the latest changes in the ASM part. 

I get the same result even if I use gcc 3.3.1 to compile it, and I
pulled a fresh cvs just before compiling with 3.3.1.  I did have to
upgrade my gdb so it could understand gcc331's debugging symbols:

Core was generated by `mpeg2enc.cvs.2003.11.04 -f 5 -n n -a 2 -V 230
-B 224 -S 8000 -b 9576 -q 10 -I 1'.
Program terminated with signal 11, Segmentation fault.
[symbol loading lines omitted]
#0  quant_non_intra_sse (wsp=Cannot access memory at address 0xbfffebd0
) at quantize_x86.c:309
309                     mulps_m2r( *(mmx_t*)&piqf[0], xmm2 );



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to