Am Wed, 19 May 2010 22:40:08 +0200
schrieb gregor herrmann gre...@debian.org:
The minimal change to make the crash go away is to remove -pie from
LDFLAGS.
So, we have some textrel issues, I suppose. I fail to see how mpg123 triggers
that, though. One observation I have, again in a VM with
On Wed, 12 May 2010 16:51:48 +0200, Thomas Orgis wrote:
Poke, poke.
Sorry for the delay, now I found some time for playing with the
flags.
Can you repeat your inital tests with the lot of files to
a) reproduce at least one original crash with the stock mpg123
b) confirm (or) not that
On Wed, 12 May 2010 16:51:48 +0200, Thomas Orgis wrote:
Yup, my test results with the current (vanilla|debian) binary+lib are
the same as yours but they are not necessarily the same as my
original crashes, and yesterday I haven't systematically tested
against the lib from testing.
But
Poke, poke.
Am Mon, 10 May 2010 22:54:15 +0200
schrieb gregor herrmann gre...@debian.org:
Yup, my test results with the current (vanilla|debian) binary+lib are
the same as yours but they are not necessarily the same as my
original crashes, and yesterday I haven't systematically tested
Hi!
On Mon, May 10, 2010 at 12:09:02AM +0200, gregor herrmann wrote:
On Sun, 09 May 2010 21:16:47 +0200, Thomas Orgis wrote:
I managed to reproduce a crash
I'm glad I'm not the only one with this phenomenon :)
With drum.mp3, I'm now also seeing the segfault in an i386 chroot. amd64 is
Am Mon, 10 May 2010 21:23:59 +0200
schrieb Daniel Kobras kob...@debian.org:
With drum.mp3, I'm now also seeing the segfault in an i386 chroot. amd64 is
still fine. Building the Debian package with DEB_BUILD_OPTIONS=noharden (ie.
without CFLAGS -Wformat -D_FORTIFY_SOURCE=2 -fstack-protector
On Mon, 10 May 2010 22:43:52 +0200, Thomas Orgis wrote:
However, I'm not sure
whether we really reproduce Gregor's original problem because for me, and
unhardened mpg123 always terminates normally even with hardened libmpg123
and
output plugin (dummy), and a hardened mpg123 always
I just added this to the mpg123 tracker item:
I managed to reproduce a crash
(no report of double free(), but a segfault during free()) on a VM install
of debian testing, with mpg123 from unstable.
The funny thing is that I observe the debian mpg123 binary crashing with
the debian libmpg123 and
On Sun, 09 May 2010 21:16:47 +0200, Thomas Orgis wrote:
I managed to reproduce a crash
I'm glad I'm not the only one with this phenomenon :)
Can you repeat what I did:
Sure, thanks for the clear and simple instructions!
1. Download the vanilla sources: http://mpg123.org/current
2. Build
Am Sat, 8 May 2010 00:12:09 +0200
schrieb gregor herrmann gre...@debian.org:
Summary:
- pulse, arts, esd, jack, nas: I have no pulse audio/artsd/esd/jackd/nas
daemon installed
- dummy: fails
- alsa: still fails
- oss: hm, somethings blocking my sound device; ah. found it later.
no
On Sat, 08 May 2010 13:04:04 +0200, Thomas Orgis wrote:
Summary:
- pulse, arts, esd, jack, nas: I have no pulse audio/artsd/esd/jackd/nas
daemon installed
- dummy: fails
- alsa: still fails
- oss: hm, somethings blocking my sound device; ah. found it later.
no visible effects on
Hi!
On Sat, May 08, 2010 at 01:24:24PM +0200, gregor herrmann wrote:
What's your setup: debian testing with mpg123 picked from unstable? System
wholly on unstable?
Almost completely unstable.
I've now set up an i386 chroot with current unstable and cannot reproduce the
problem there,
On Sat, 08 May 2010 15:39:42 +0200, Daniel Kobras wrote:
I've now set up an i386 chroot with current unstable and cannot reproduce the
problem there, either. Do you see the error with any mp3, or just with
specific
files?
I've now tried with 77 small mp3s [0] from my hard disk, and the
Hi, this is mpg123 upstream.
I asked for some confirmation of the confinedness of the issue to the ALSA
output on
http://sourceforge.net/tracker/?func=detailaid=2996045group_id=135704atid=733194
...
Actually, this concerns both issues: The crash and the high CPU usage. Can you
try another
On Fri, 07 May 2010 23:13:45 +0200, Thomas Orgis wrote:
Hi, this is mpg123 upstream.
Hi!
I asked for some confirmation of the confinedness of the issue to
the ALSA output on
http://sourceforge.net/tracker/?func=detailaid=2996045group_id=135704atid=733194
...
Ah, sorry, I haven't followed
Package: libmpg123-0
Version: 1.12.1-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The new version of libmpg123-0 (1.12.1-1) causes mpg123 to explode
after playing a song; and while playing the song mpg123 uses insane
amounts of CPU.
Hi!
On Mon, May 03, 2010 at 05:50:08PM +0200, gregor herrmann wrote:
The new version of libmpg123-0 (1.12.1-1) causes mpg123 to explode
after playing a song; and while playing the song mpg123 uses insane
amounts of CPU.
Thanks for the report. I didn't notice this behaviour while testing the
On Mon, 03 May 2010 19:25:54 +0200, Daniel Kobras wrote:
The new version of libmpg123-0 (1.12.1-1) causes mpg123 to explode
after playing a song; and while playing the song mpg123 uses insane
amounts of CPU.
Thanks for the report. I didn't notice this behaviour while testing the
package
18 matches
Mail list logo
