Bug#762876: named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c

2014-09-28 Thread Christoph Anton Mitterer
On my system here, it quite reproducibly crashes when I start bind, and then more or less directly after starting, ping security.debian.org Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature

Bug#762876: named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c

2014-09-28 Thread Christoph Anton Mitterer
On my system here, it quite reproducibly crashes when I start bind, and then more or less directly after starting, ping security.debian.org Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature

Bug#762876: named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c

2014-09-26 Thread S. R. Wright
I can confirm that a rollback to version 1:9.9.5.dfsg-4 works correctly. My name server is just caching-only. -- sRw -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#762876: named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c

2014-09-26 Thread Christoph Anton Mitterer
Same here: 25-Sep-2014 07:25:13.497 general: critical: mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace later again: 26-Sep-2014 03:11:41.432 general: critical: mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace 26-Sep-2014 03:11:41.432 general: critical: #0 0x7f6a7776722d in