severity 602668 serious tag 602668 sid thanks On Thu, Jul 05, 2012 at 04:15:46AM +0200, Salvatore Bonaccorso wrote: > On Thu, Nov 11, 2010 at 10:54:58PM +0200, Niko Tyni wrote: > > severity 602668 important > > clone 602668 -1 > > retitle -1 gdb: 7.2 falsely (?) shows stack corruption on armel > > reassign -1 gdb 7.2-1 > > block 602668 with -1 > > thanks > > > > On Sat, Nov 06, 2010 at 11:15:01PM +0000, Hector Oron wrote: > > > Package: libdevel-bt-perl > > > Version: 0.05-1 > > > Severity: serious > > > > It's never built on armel yet, so downgrading. > > Just noticed this looking at the pkg-perl 'dashboard': In the > 'meantime' it seems that libdevel-bt-perl was once build already too > on armel. But 0.06-1 did not succeed again[1]. > > [1]: > https://buildd.debian.org/status/logs.php?pkg=libdevel-bt-perl&arch=armel
That makes this RC for 0.06-1 and blocks its testing migration. However, given the past history and the tight coupling with gdb, I suspect 0.05-1 in wheezy is also affected. Tagging 'sid' for now (and I hope that's the right thing to do), but it would be good to verify if it currently builds in wheezy on armel. FWIW, here's a summary of the build logs. The failure mode seems to have changed a bit with the gdb 7.4 builds: the logs now indicate an empty backtrace instead of a corrupted one. source_version gdb_version perl_version result notes 0.05-1 7.2-1 5.10.1-14 FAIL 5 failures 0.05-1 7.2-1 5.10.1-18 FAIL 5 failures 0.05-1 7.3-1 5.12.4-4 OK 0.05-1 7.3-1+b1 5.14.2-3 OK 0.06-1 7.4really-1 5.14.2-7 FAIL 1 failure 0.06-1 7.4.1-1.1 5.14.2-9 FAIL 4 failures BTW, gdb_7.4.1-1.1 fixes "LinuxThreads signal handling on GNU/kFreeBSD", so it might be worth a try to reschedule this on kfreebsd-amd64 which has been failing consistently up to and including 7.4really-1 with related symptoms. -- Niko Tyni [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
