From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8321] New: invalid opcode error with minidlna and ffmpeg
Date: Sun, 30 Aug 2015 19:52:33 +0000 (UTC) [thread overview]
Message-ID: <bug-8321-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8321
Summary: invalid opcode error with minidlna and ffmpeg
Product: buildroot
Version: 2015.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: ramesh at rr7.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Have a strange issue... I keep getting invalid opcode errors when minidlna is
scanning my files. The scanner then stops. I get these sort of errors in
dmesg...
traps: minidlnad[2435] trap invalid opcode ip:7fb52ca30120 sp:7fff7745e1a8
error:0 in libavutil.so.54.20.100[7fb52ca1b000+4c000]
Running 2015.05 with ffmpeg 2.6.2 and minidlna 1.1.4
ffmpeg version up to 2.5.8 work fine. Everything from 2.6.1 onwards causes
various versions of the above error. I cannot seem to debug it - any help is
very welcome. Thanks.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-08-30 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 19:52 bugzilla at busybox.net [this message]
2015-10-14 9:44 ` [Buildroot] [Bug 8321] invalid opcode error with minidlna and ffmpeg bugzilla at busybox.net
2015-11-25 13:46 ` bugzilla at busybox.net
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=bug-8321-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.