[Pm-utils] Re: HAL Crasher

Richard Hughes hughsient at gmail.com
Wed Mar 14 17:11:06 PDT 2007

On Thu, 2007-03-15 at 00:06 +0000, Richard Hughes wrote:
> HAL really shouldn't crash. I've got no time to debug this now. Release
> blocker?

(gdb) bt
#0  0x007d4402 in __kernel_vsyscall ()
#1  0x00288f60 in raise () from /lib/libc.so.6
#2  0x0028a7b1 in abort () from /lib/libc.so.6
#3  0x02df8f55 in _dbus_abort () at dbus-sysdeps.c:84
#4  0x02df4ee6 in _dbus_warn_check_failed (
    format=0x2e00860 "arguments to %s() were incorrect, assertion \"%s\"
failed in file %s line %d.\nThis is normally a bug in some application
using the D-Bus library.\n")
    at dbus-internals.c:283
#5  0x02de97d4 in dbus_message_new_error (reply_to=0x9a9f638, 
    error_name=0x9adb3c4 "/usr/lib/pm-utils/power.d/laptop-tools: line
5: /etc/pm/functions: No such file or directory",
error_message=0x9adb428 "") at dbus-message.c:1206
#6  0x0805963f in hald_exec_method_cb (d=0x9a8c5d0, exit_type=0,
return_code=0, error=0x9a91688, data1=0x9a9f638, data2=0x9a8efa8) at
#7  0x0804ed0b in process_reply (m=0x9a98378, hb=0x9aa1ae0) at
#8  0x0804ed31 in call_notify (pending=0x9ac5848, user_data=0x9aa1ae0)
at hald_runner.c:689
#9  0x02deb231 in _dbus_pending_call_complete (pending=0x9ac5848) at
#10 0x02ddbca3 in complete_pending_call_and_unlock
(connection=0x9a923e8, pending=0x9ac5848, message=<value optimized out>)
at dbus-connection.c:2166
#11 0x02ddd6d6 in dbus_connection_dispatch (connection=0x9a923e8) at
#12 0x00d04c7d in message_queue_dispatch (source=0x9a92470, callback=0,
user_data=0x0) at dbus-gmain.c:113
#13 0x001ec622 in IA__g_main_context_dispatch (context=0x9a8dd58) at
#14 0x001ef5ff in g_main_context_iterate (context=0x9a8dd58, block=1,
dispatch=1, self=0x9a8f280) at gmain.c:2677
#15 0x001ef9a9 in IA__g_main_loop_run (loop=0x9a8c6d0) at gmain.c:2881
#16 0x08055faf in main (argc=3, argv=0xbfc3fe44) at hald.c:624


More information about the Pm-utils mailing list