From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: ffmpeg segfault with musl
Date: Wed, 18 Sep 2019 09:50:36 -0400 [thread overview]
Message-ID: <20190918135036.GA9017@brightrain.aerifal.cx> (raw)
In-Reply-To: <150f8535-83a7-b7a0-d11d-8efc54d60348@direct.lv>
On Wed, Sep 18, 2019 at 04:22:06PM +0300, JS wrote:
> Hello
>
> Does anybody have experience/solution with ffmpeg segfaulting with
> musl? The issue happens when mpd tries to play wav file that is
> decoded by ffmpeg. Tested with musl 1.1.17 and 1.1.23 and both old
> and new ffmpeg versions. This does not happen with uClibc on the
> same hardware.
I'm not aware of any such problem. Are there publicly available files
you can reproduce the crash with? Is mpd necessary or does ffplay
crash too? (easier test case)
Rich
next prev parent reply other threads:[~2019-09-18 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 13:22 JS
2019-09-18 13:50 ` Rich Felker [this message]
2019-09-18 16:13 ` A. Wilcox
2019-09-18 18:31 ` Natanael Copa
2019-09-18 19:14 ` JS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190918135036.GA9017@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).