Bug#523261: [Monotone-debian] Bug#523261: monotone segfaulting on any invocation

[Gary Kramlich]

Zack Weinberg wrote:
> On Wed, Apr 8, 2009 at 9:09 PM, Gary Kramlich <address@hidden> wrote:
>> any invocation of mtn is causing a segfault.  I have a core, but contains a 
>> single frame of:
>>
>> #0  0x0000000000000000 in _start () from /lib64/ld-linux-x86-64.so.2
>>
>> Even a simple "mtn --version" outside of a working copy results in a 
>> segfault.
> 
> This is not reproducible on my system, which is also amd64 sid with
> the same versions for all dependent libraries.
> 
> Crashing in _start() suggests that some library or executable on the
> system is corrupted.   Please install the "debsums" package and run
> this command:
> 
> # debsums -s monotone libbotan1.8 libc6 libgcc1 libidn11 liblua5.1-0
> libpcre3 libsqlite3-0 libstdc++6 zlib1g
> 
> If this prints any lines of the form
> 
> debsums: checksum mismatch libpcre3 file /usr/lib/libpcreposix.so.3.12.1
> 
> then please reinstall the packages named right after "checksum
> mismatch" (libpcre3, in the example).  And let us know if that solves
> the problem.  You may also want to run a forcible fsck and/or a hard
> drive sector read test.
> 
> If this advice does *not* solve the problem, then please post the
> complete output of this command:
> 
> $ LD_DEBUG=files mtn --version
> 
> Thanks,
> zw

Ok, it get's even weirder... mtn works fine on tty0, but fails under X.
 Also, works fine as root under X.

$ mtn --version
Segmentation fault
$ sudo mtn --version
monotone 0.43 (base revision: ddc6546051abf6475c40a3fdba272e2f82a40e94)

I moved ~/.monotone out of the way, and that didn't make a difference.
I'm comparing environment variables at the moment, but haven't come
across anything yet.  Going to try tinkering with $PATH next.

-- 
Gary Kramlich <address@hidden>