[x264-devel] [Måns Rullgård <mru at inprovide.com>] Re: x264 rev 146 segmentation fault

[System administration]

The enclosed valgrind trace was far too long within the mail.
It has been detached and can now be found at 
  http://www.videolan.org/~admin/20050303-videolan/valgrind_trace
  

----- Forwarded message from Måns Rullgård <mru at inprovide.com> -----

From: Måns Rullgård <mru at inprovide.com>
Date: Wed, 02 Mar 2005 21:43:49 +0100
To: x264-devel at videolan.org
Subject: Re: [x264-devel] x264 rev 146 segmentation fault
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
X-Spam-Status: No, score=-1.7 required=5.0 tests=FORGED_RCVD_HELO,IN_REP_TO,
	RCVD_IN_NJABL_DUL,RCVD_IN_ORBS autolearn=failed version=3.0.2

Tuukka Toivonen <tuukkat at ee.oulu.fi> writes:

> I get segmentation fault from x264 with some videos.
> Optimizations levels or CPU-specific things (e.g. -DARCH_X86) don't
> seem to make a difference, but I am linking x264 with Electric Fence:
> -       $(CC) $(CFLAGS) -o x264 x264.o libx264.a -lm
> +       $(CC) $(CFLAGS) -o x264 x264.o libx264.a -lefence -lm
>
> One example test video is here:
> http://www.ee.oulu.fi/~tuukkat/tmp/sg2ac-720x576.yuv.bz2
> (please make a copy, I don't want to leave it there for a long time)

I've placed a copy at http://mru.ath.cx/samples/sg2ac-720x576.yuv.bz2

> Sorry, no patch this time, but here's a gdb trace:

In case it helps, here's a valgrind trace:

-- 
Måns Rullgård
mru at inprovide.com

// eompost 42262590:599B.1:kqriry


----- End forwarded message -----

-- 
System administration <admin at via.ecp.fr>
VIA, Ecole Centrale Paris, France

-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html