[systemd-bugs] [Bug 69643] systemdadm double free or corruption

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Dec 8 05:06:31 PST 2013


https://bugs.freedesktop.org/show_bug.cgi?id=69643

--- Comment #2 from Michael Stapelberg <michael+freedesktop at stapelberg.de> ---
I can reproduce this with the current git HEAD (commit
0bfc54dedd309b3e265fb8d514e58ac1c67811af) and systemd-204 on Debian. This has
also been reported as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731387
in Debian.

Steps to reproduce:
1) launch systemadm
2) sudo systemctl stop miredo.service

The backtrace is:

#0  0x00007fdc978851e5 in __GI_raise (sig=sig at entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007fdc97888398 in __GI_abort () at abort.c:90
#2  0x00007fdc978c07cb in __libc_message (do_abort=do_abort at entry=2, 
    fmt=fmt at entry=0x7fdc979bcbe8 "*** Error in `%s': %s: 0x%s ***\n")
    at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
#3  0x00007fdc978caa26 in malloc_printerr (action=3, 
    str=0x7fdc979b8b8a "free(): invalid pointer", ptr=<optimized out>) at
malloc.c:4902
#4  0x00007fdc978cb7a3 in _int_free (av=<optimized out>, 
    p=0x624648 <g_define_type_id__volatile.26118>, have_lock=0) at
malloc.c:3758
#5  0x000000000041a00c in job_unit_link_destroy
(self=self at entry=0x7ffffa64b430)
    at /tmp/systemd-ui/src/systemd-interfaces.vala:151
#6  0x00000000004095d0 in main_window_update_job_iter
(self=self at entry=0x69c070, 
    iter=iter at entry=0x7ffffa64b530, id=id at entry=705, j=0xa548c0)
    at /tmp/systemd-ui/src/systemadm.vala:767
#7  0x000000000040acea in main_window_on_job_new (self=0x69c070, id=705, 
    path=0x8ce960 "/org/freedesktop/systemd1/job/705")
    at /tmp/systemd-ui/src/systemadm.vala:795
#8  0x00007fdc983d6f28 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x00007fdc983e7edd in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007fdc983efce9 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007fdc983f0462 in g_signal_emit_by_name ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00000000004139b6 in _dbus_handle_manager_job_new (parameters=<optimized
out>, 
    self=0x7af1b0) at systemd-interfaces.c:1506
#13 manager_proxy_g_signal (proxy=0x7af1b0, sender_name=<optimized out>, 
    signal_name=<optimized out>, parameters=<optimized out>) at
systemd-interfaces.c:1541
#14 0x00007fdc94651e28 in ffi_call_unix64 () from
/usr/lib/x86_64-linux-gnu/libffi.so.6
#15 0x00007fdc94651790 in ffi_call () from
/usr/lib/x86_64-linux-gnu/libffi.so.6
#16 0x00007fdc983d7768 in g_cclosure_marshal_generic ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007fdc983d6f28 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007fdc983e7c9b in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007fdc983efce9 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007fdc983eff32 in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007fdc986da21c in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#22 0x00007fdc986cace5 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#23 0x00007fdc9810fea6 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007fdc981101f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fdc981105fa in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007fdc98afc39d in gtk_main () at
/tmp/buildd/gtk+3.0-3.8.4/./gtk/gtkmain.c:1156
#27 0x000000000040c595 in _vala_main (args=0x7ffffa64c478, args_length1=1)
    at /tmp/systemd-ui/src/systemadm.vala:1074
#28 0x00007fdc97871995 in __libc_start_main (main=0x4049a0 <main>, argc=1, 
    ubp_av=0x7ffffa64c478, init=<optimized out>, fini=<optimized out>, 
    rtld_fini=<optimized out>, stack_end=0x7ffffa64c468) at libc-start.c:260
#29 0x00000000004049fc in _start ()

I have attached the output of “backtrace full” as an attachment.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20131208/b8ef69ca/attachment.html>


More information about the systemd-bugs mailing list