On Thu, Apr 9, 2009 at 6:57 PM, Gary Kramlich <g...@reaperworld.com> wrote: > > debsums found nothing. all my filesystems were in pretty bad shape, > somehow the journals kept them alive. They're all clean now, problem > persists.
Ok. > g...@cloak:~$ LD_DEBUG=files mtn --version > 8031: > 8031: file=libm.so.6 [0]; needed by mtn [0] > 8031: file=libm.so.6 [0]; generating link map > 8031: dynamic: 0xf7f30ef0 base: 0xf7f0e000 size: 0x00023080 > 8031: entry: 0xf7f11410 phdr: 0xf7f0e034 phnum: 9 > 8031: file=libc.so.6 [0]; needed by mtn [0] > 8031: file=libc.so.6 [0]; generating link map > 8031: dynamic: 0xf7f09d7c base: 0xf7db6000 size: 0x00157650 > 8031: entry: 0xf7dcc87e phdr: 0xf7db6034 phnum: 10 > 8031: calling init: /lib32/libc.so.6 > 8031: calling init: /lib32/libm.so.6 > 8031: initialize program: mtn > Segmentation fault Something is very, very wrong here. The 0.43 mtn binary is linked against many more libraries than that, and that output is showing 32-bit pointers and loading libs from /lib32. Are you sure the package you've got is the official sid package of monotone 0.43? What does 'ldd /usr/bin/mtn' print? What is the first stanza of /usr/share/doc/monotone/changelog.Debian.gz ? zw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
