From owner-freebsd-questions@FreeBSD.ORG Thu Nov 15 09:19:01 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D45316A421 for ; Thu, 15 Nov 2007 09:19:01 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 14BE413C48A for ; Thu, 15 Nov 2007 09:19:00 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.37] (a89-182-174-138.net-htp.de [89.182.174.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 3A26BA44529 for ; Thu, 15 Nov 2007 10:12:55 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-questions@freebsd.org Date: Thu, 15 Nov 2007 10:19:52 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711151019.52932.wundram@beenic.net> Subject: ffmpeg demuxer library currently broken? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 09:19:01 -0000 Hey all! Does anyone else have problems with the latest ffmpeg port (from Oct 20)? It crashes "reliably" for me transcoding any input to any output (I tested with avi and mp3 files). The backtrace in the core-dump is corrupt, but it seems that the problem lies somewhere in libavformat's demuxer library (but is format independent), which causes a segmentation fault. If anybody else is experiencing this, please write me a short mail, because I'll start investigating deeper under that circumstance (I need ffmpeg desperately for work, and simply downgraded to the previous port, which works fine, but still would like to have a fix for the current ffmpeg if it's not only my system that is causing this). Thanks for any info! -- Heiko Wundram Product & Application Development