yelp crashed with SIGSEGV in malloc()

[dust]

Binary package hint: yelp

was looking after iptables and opened a link in a new window

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: nvidia
Package: yelp 2.24.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: yelp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: yelp
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 operator new () from /usr/lib/libstdc++.so.6
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
Title: yelp crashed with SIGSEGV in malloc()
Uname: Linux 2.6.27-8-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
operator new (sz=16)
nsThebesRenderingContext::Init (this=0x91f9ad8,
nsBaseWidget::GetRenderingContext (this=0x9191970)

[Chris Coulson (chrisccoulson)]

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.

[dust (hannes-b)]

thanks for your help!

[quote]...t:~$ sudo apt-get install valgrind
Reading package lists... Done
Building dependency tree
Reading state information... Done
valgrind is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
...:~$ rm valgrind.log.*
rm: cannot remove `valgrind.log.*': No such file or directory
...:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log <program> <arguments>
bash: syntax error near unexpected token `<'
...:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
valgrind: no program specified
valgrind: Use --help for more information.
...:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log <yelp>
bash: syntax error near unexpected token `newline'
[/quote]

which argument should i use?

best regards

[Chris Coulson (chrisccoulson)]

You don't need to run yelp with any additional arguments. You just need to run:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log yelp

Before you do this though, you will probably need to install some debugging symbols. The procedure for doing this is detailed in https://wiki.ubuntu.com/DebuggingProgramCrash. Please add the necessary repositories as detailed in this URL, then run the following to install the debugging symbols that I think you'll need:

sudo apt-get install yelp-dbgsym libc6-dbgsym libc6-i686-dbgsym libstdc++6-dbgsym xulrunner-1.9-dbgsym libgtk2.0-0-dbgsym libglib2.0-0-dbgsym

[dust (hannes-b)]

thanks for the help and best regards!

[dust (hannes-b)]

any news? why is the status still incomplete?

[Chris Coulson (chrisccoulson)]

Re-attaching the valgrind log in plaintext, so I can link to it from the upstream bug tracker

[Chris Coulson (chrisccoulson)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=560917

[Chris Coulson (chrisccoulson)]

dust - from the upstream bug report:

"The valgrind log doesn't seem to have resulted from the same programme run that
produced the crash, so offers no info on it. The crash itself is in gecko code.

The valgrind log however does contains some mem leaks and invalid reads in yelp
and rarian, which should be fixed separately of course."

Would you mind providing another valgrind log from a run where the crash occurs?

Thanks

[Pedro Villavicencio (pedro)]

could you provide another log or shall we close the report?

[dust (hannes-b)]

i will try todo it again this weekend

[Sebastien Bacher (seb128)]

did you try to get a new log?

[dust (hannes-b)]

thanks for the reminder!

sorry, lost the track after several hundred posts about bugs i get from launchpad and all goes in one mailbox...

the new log will come.

[dino99 (9d9)]

This version has expired long time ago, and is no more supported