From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: bug: audio/oggenc crash
Date: Sat, 8 Sep 2018 18:17:25 -0700 [thread overview]
Message-ID: <CAH_zEu686GXOG4f2U17hufvNUq2Of60i5tyRokW6EaXNhojFtw@mail.gmail.com> (raw)
In-Reply-To: <CAH_zEu5_S3jc60Tghg-UO_ememOGaNiKH3GyN7dLX2WWNLyyYA@mail.gmail.com>
fixed in 2f306838edbf.
On Fri, Sep 7, 2018 at 7:27 PM Nick Owens <mischief@offblast.org> wrote:
>
> when oggenc is run, it appears to always eventually crash:
>
> cpu% audio/oggenc < /dev/zero > /dev/null
> cpu% echo $status
> oggenc 4556069: abort
>
> the abort occurs due to free() called on a corrupted malloc()'d buffer
> inside of libvorbis.
>
> this call to malloc was inserted as a replacement for alloca(), which
> of course we don't have. perhaps this bug was always in this code, but
> never noticed since it might just trash autos on the stack.
prev parent reply other threads:[~2018-09-09 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 2:27 Nick Owens
2018-09-09 1:17 ` Nick Owens [this message]
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=CAH_zEu686GXOG4f2U17hufvNUq2Of60i5tyRokW6EaXNhojFtw@mail.gmail.com \
--to=mischief@offblast.org \
--cc=9front@9front.org \
/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 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).