notify-osd crashed with SIGSEGV in realloc()

[nilswerner22]

Binary package hint: notify-osd

i use jaunty alpha 6. the crash happened while using cgmail. occurs seldom

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
Package: notify-osd 0.9.6-0ubuntu2
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 realloc () from /lib/tls/i686/cmov/libc.so.6
 g_realloc () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: notify-osd crashed with SIGSEGV in realloc()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:_int_malloc (av=0xb7898140, bytes=33) at malloc.c:4202
_int_realloc (av=0xb7898140, oldmem=0x8ef96c0, bytes=36)
*__GI___libc_realloc (oldmem=0x8ef96c0, bytes=36)
IA__g_realloc (mem=0x8ef96c0, n_bytes=36)
type_node_add_iface_entry_W (node=0x8ef4c40,

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[Juan Sebastián Marulanda (juanchito2006)]

I'm having this issue on Karmic quite constantly, for no apparent reason.

[Pedro Villavicencio (pedro)]

could you provide the valgrind log ? Thanks.

[Juan Sebastián Marulanda (juanchito2006)]

I'm not sure how to make such log, This is my console output:

$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log notify-osd
valgrind: notify-osd: command not found

[Alexey Kotlyarov (koterpillar)]

I believe you should use CmdLine from crash output:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log notify-osd /usr/lib/notify-osd/notify-osd

[Juan Sebastián Marulanda (juanchito2006)]

I'm getting the same output:

$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log notify-osd /usr/lib/notify-osd/notify-osd
valgrind: notify-osd: command not found

[Alexey Kotlyarov (koterpillar)]

My bad, the right line will be:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/notify-osd/notify-osd
Also, you'll have to
1) kill notify-osd (killall notify-osd) which would be already running then, otherwise your new instance will immediately exit
2) reproduce the crash (use cgmail?)

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.