[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xbindkeys-devel] Re: [xbindkeys] Crash. Some questions and probably fix
From: |
Philippe Brochard |
Subject: |
[Xbindkeys-devel] Re: [xbindkeys] Crash. Some questions and probably fix |
Date: |
Fri, 03 Dec 2010 21:33:48 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) |
Anatoly Bashmakov writes:
> Philippe Brochard wrote:
>> ...
>> 1) try valgrind with those options:
>>
>> --track-origins=yes --leak-check=full --show-reachable=yes
>>
>> 2) Test with electric fence (maybe more simple to use)
>>
>> 3) try to compile xbindkeys without the guile support. I have the same
>> guile version but it's maybe a cause of problems.
>>
>
> Outputs of
>
> $ valgrind --track-origins=yes --leak-check=full \
> --show-reachable=yes --log-file=xbindkeys_valgrind.log \
> --tool=memcheck ./xbindkeys -n
>
> and
>
> $ valgrind -v --track-origins=yes --leak-check=full \
> --show-reachable=yes --log-file=xbindkeys_valgrind_v.log \
> --tool=memcheck ./xbindkeys -n
>
> attached (xbindkeys was built without guile).
>
> Unfortunately, electric fence and duma segfault with xbindkeys (or maybe
> I do smth wrong)
>
> $ ef ./xbindkeys -n
>
> Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
> <address@hidden>
> DEBUG: envstr=DISPLAY=:0 string=:0
> /usr/bin/ef: line 20: 32694 Segmentation fault ( export
> LD_PRELOAD=libefence.so.0.0; exec $* )
> $
>
>
> $ duma ./xbindkeys -n
> DUMA 2.5.15 (shared library)
> Copyright (C) 2006 Michael Eddington <address@hidden>
> Copyright (C) 2002-2008 Hayati Ayguen <address@hidden>, Procitec GmbH
> Copyright (C) 1987-1999 Bruce Perens <address@hidden>
>
> DEBUG: envstr=DISPLAY=:0 string=:0
> /usr/bin/duma: line 17: 32679 Segmentation fault ( export
> LD_PRELOAD=/usr/lib/libduma.so.0.0.0; export
> DYLD_INSERT_LIBRARIES=libduma.dylib; export DYLD_FORCE_FLAT_NAMESPACE=1; exec
> $* )
> $
>
If they segfault, it's because there is a memory problem somewhere.
You can try to debug them with gdb. duma is better because gdb will
point you to the line in cause.
I'm updating my Archlinux to libX11-1.4.0 and I'll see if I can
reproduce the bug.
Another test you can do is to compile xbindkeys with disabled fork.
Regards,
Philippe
- [Xbindkeys-devel] Re: [xbindkeys] Crash. Some questions and probably fix,
Philippe Brochard <=