hal 0.5.8.1 released

[Kay Sievers]

On Fri, 2006-09-22 at 08:54 -0700, Artem Kachitchkine wrote:
> > hald will segfault while the hald-addons will continue to run.
> 
> If there's a coredump from the 'hald' process, that would help pinpoint 
> what part of code is at fault.

Mark, maybe you can try to run it in gdb and get a stack backtrace?

Thanks,
Kay

$ gdb /usr/sbin/hald
(gdb) r --daemon=no --verbose=yes
...
Program received signal ..., Aborted.
[Switching to Thread -1211894096 (LWP 13620)]
0xb7f0d410 in ?? ()
(gdb) bt
#0  0xb7f0d410 in ?? ()
#1  0xbf9dea28 in ?? ()
#2  0x000069c7 in ?? ()
#3  0x0000000a in ?? ()
#4  0xb7d08d1b in poll () from /lib/libc.so.6
#5  0xb7e3777b in g_main_context_query (context=0x816bd80,
max_priority=10, 
    timeout=0x69c7, fds=0x816bd80, n_fds=10) at gmain.c:2420
#6  0xb7e3be53 in g_main_context_iterate (context=0x808db60, block=1, 
    dispatch=1, self=0x808e668) at gmain.c:2979
#7  0xb7e3c1c9 in g_main_loop_run (loop=0x808dbe0) at gmain.c:2881
#8  0x0805669e in main (argc=3, argv=0xbf9deec4) at hald.c:582
#9  0xb7c6a87c in __libc_start_main () from /lib/libc.so.6
#10 0x0804cc01 in _start ()