On Wed, Dec 16, 2009 at 09:33:53PM +0100, Marco d'Itri wrote:
> On Dec 16, Josip Rodin <[email protected]> wrote:
>
> > I've no idea where to look, please advise.
> Me neither. For a start you could use strace to find out how udevadm is
> being called and try to reproduce the issue.
In an apparent twist, I tried stracing the startx, and now suddenly there is
no longer a problem - it just works, with or without strace. So I retraced
my steps when I initially reported the two bugs and found the actual trigger:
% sudo /etc/init.d/hal restart
Restarting Hardware abstraction layer: haldudevadm[2063]: segfault at 0 ip
00007ff3ea90d7c1 sp 00007fff6acb6098 error 4 in
libc-2.10.2.so[7ff3ea894000+14a000]
udevadm[2064]: segfault at 0 ip 00007f85d1ebc7c1 sp 00007fffca9a1038 error 4 in
libc-2.10.2.so[7f85d1e43000+14a000]
udevadm[2065]: segfault at 0 ip 00007f964fc957c1 sp 00007fffe0bad6c8 error 4 in
libc-2.10.2.so[7f964fc1c000+14a000]
udevadm[2066]: segfault at 0 ip 00007fd91af0f7c1 sp 00007fff0a09ce88 error 4 in
libc-2.10.2.so[7fd91ae96000+14a000]
udevadm[2067]: segfault at 0 ip 00007fa4bf8e67c1 sp 00007fff371476c8 error 4 in
libc-2.10.2.so[7fa4bf86d000+14a000]
udevadm[2068]: segfault at 0 ip 00007f15857e47c1 sp 00007fff10be9938 error 4 in
libc-2.10.2.so[7f158576b000+14a000]
udevadm[2069]: segfault at 0 ip 00007f20458ec7c1 sp 00007fffb78683c8 error 4 in
libc-2.10.2.so[7f2045873000+14a000]
udevadm[2070]: segfault at 0 ip 00007f456ada97c1 sp 00007fff415ea188 error 4 in
libc-2.10.2.so[7f456ad30000+14a000]
udevadm[2071]: segfault at 0 ip 00007fdea377f7c1 sp 00007fff52867778 error 4 in
libc-2.10.2.so[7fdea3706000+14a000]
.
%
Stopping it and just running /usr/sbin/hald manually provokes the segfaults.
However running strace -f -o hald.strace.log /usr/sbin/hald
creates a large log file that generates around 1.7MB of output, no segfaults,
and then it stalls on some poll() call, occasionally continuing.
Thoughts?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
