[Ian Jackson]
> It works fine under valgrind (!).
How strange. It ran without crashing here too, for what that is worth.
Were there any messages at all from valgrind? Uninitialized memory or
anything vagely related?
> Program received signal SIGSEGV, Segmentation fault.
> __lll_unlock_elision
Petter Reinholdtsen writes ("Re: Bug#842796: ogg123 always segfaults after
playing file"):
> [Ian Jackson]
> > This started happening after I moved my OS install to a new computer.
> > But I also probably did an apt-get upgrade. So the trigger was
> > probab
Petter Reinholdtsen writes ("Re: Bug#842796: ogg123 always segfaults after
playing file"):
> [Ian Jackson]
> > It works fine under valgrind (!).
>
> How strange. It ran without crashing here too, for what that is worth.
> Were there any messages at all from val
[Ian Jackson]
> This started happening after I moved my OS install to a new computer.
> But I also probably did an apt-get upgrade. So the trigger was
> probably either an update, or running on a new CPU.
That sound nasty. Can you try to install debug symbols and see if you
can reproduce the
Package: vorbis-tools
Version: 1.4.0-6+deb8u1
Severity: important
$ rm Example.ogg
$ wget https://upload.wikimedia.org/wikipedia/commons/c/c8/Example.ogg
--2016-11-01 11:26:32--
https://upload.wikimedia.org/wikipedia/commons/c/c8/Example.ogg
Resolving upload.wikimedia.org
5 matches
Mail list logo
