monotone-debian
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-debian] Monotone completely broken in Debian testing (I think)


From: Francis Russell
Subject: [Monotone-debian] Monotone completely broken in Debian testing (I think)
Date: Mon, 09 Jul 2012 22:19:11 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4

Monotone broke for me completely today in that I couldn't even run mtn
with no options on my x86_64 Debian testing system. Based on the
backtrace I got from GDB and my APT logs, it looks like the upgrade of
libbotan1.10-0 from 1.10.1-1 to 1.10.2-1 is the culprit:

address@hidden:~$ gdb /usr/bin/mtn
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show co
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mtn...(no debugging symbols found)...d
(gdb) run
Starting program: /usr/bin/mtn
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.

Program received signal SIGSEGV, Segmentation fault.
0x00000000005cf99c in Botan::SHA_160::~SHA_160() ()
(gdb) bt
#0  0x00000000005cf99c in Botan::SHA_160::~SHA_160() ()
#1  0x00007ffff77f8b66 in Botan::Hash_Filter::~Hash_Filter() () from
#2  0x00007ffff780ddec in Botan::Pipe::destruct(Botan::Filter*) () f
#3  0x00007ffff780de58 in Botan::Pipe::~Pipe() () from /usr/lib/libb
#4  0x00007ffff78cfdb3 in ?? () from /usr/lib/libbotan-1.10.so.0
#5  0x00007ffff78d06b0 in Botan::algorithm_kat(Botan::SCAN_Name
conslocator<std::pair<std::string const, std::string> > > const&, Botan:
#6  0x00007ffff78d4b43 in ?? () from /usr/lib/libbotan-1.10.so.0
#7  0x00007ffff78d5603 in Botan::confirm_startup_self_tests(Botan::A
#8  0x00007ffff7836257 in Botan::Library_State::initialize(bool) ()
#9  0x00007ffff7834df4 in Botan::LibraryInitializer::initialize(std:
#10 0x00000000006d7b3a in ?? ()
#11 0x00000000004193ba in ?? ()
#12 0x00007ffff6288ead in __libc_start_main (main=<optimized out>, a
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ff
#13 0x0000000000419491 in ?? ()
#14 0x00007fffffffe208 in ?? ()
#15 0x000000000000001c in ?? ()
#16 0x0000000000000001 in ?? ()
#17 0x00007fffffffe53a in ?? ()
#18 0x0000000000000000 in ?? ()
(gdb)

Once I rebuilt the package, mtn worked fine so I guess Botan made some
incompatible ABI change. Can someone else confirm what I've seen?
Unfortunately, the only other thing that uses botan1.10-0 is softhsm as
I couldn't convince it to do anything that confirmed the issue was with
Botan.

What's the easiest way to get this fixed?

Francis



reply via email to

[Prev in Thread] Current Thread [Next in Thread]