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 > against the lib from testing. > But since I was not able to reliably reproduce the crashes it's no > big help anyway ... 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 you do not manage to produce that crash with self-built mpg123 ? Then... the obvious way would be to find out which one of the hardened flags Daniel mentioned breaks mpg123. So... write a script that iterates over the flags, and builds mpg123 with a reasonable subset of the combinations. CFLAGS=... ./configure ... --with-optimization=0 # The latter option to really only use your CFLAGS. I'd like to see where this one is going. Will there be a bug to fix in mpg123 or not? Alrighty then, Thomas.
signature.asc
Description: PGP signature
