memcheck-x86-linux crashed with SIGSEGV in do_syscall_WRK()

Bug #826982 reported by David Kastrup
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
valgrind (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Not sure whether this may be a duplicate of an existing bug, but the last open report is from several years ago.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: valgrind 1:3.6.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
Architecture: i386
Date: Mon Aug 15 22:36:09 2011
ExecutablePath: /usr/lib/valgrind/memcheck-x86-linux
ProcCmdline: /usr/bin/valgrind.bin out/bin/lilypond input/regression/tablature-string-tunings.ly
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: valgrind
Stacktrace:
 #0 0x3803cda6 in do_syscall_WRK ()
 No locals.
 Backtrace stopped: Not enough registers or memory available to unwind further
StacktraceTop: do_syscall_WRK ()
ThreadStacktrace:
 .
 Thread 1 (LWP 23704):
 #0 0x3803cda6 in do_syscall_WRK ()
 No locals.
 Backtrace stopped: Not enough registers or memory available to unwind further
Title: memcheck-x86-linux crashed with SIGSEGV in do_syscall_WRK()
UpgradeStatus: Upgraded to oneiric on 2011-07-25 (21 days ago)
UserGroups: adm admin audio cdrom dialout floppy lpadmin plugdev sambashare sudo

Revision history for this message
David Kastrup (dak) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x3803cda6 in do_syscall_WRK ()
 No locals.
 Backtrace stopped: Not enough registers or memory available to unwind further
StacktraceTop: do_syscall_WRK ()
ThreadStacktrace:
 .
 Thread 1 (LWP 23704):
 #0 0x3803cda6 in do_syscall_WRK ()
 No locals.
 Backtrace stopped: Not enough registers or memory available to unwind further

Changed in valgrind (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in valgrind (Ubuntu):
status: New → Confirmed
Revision history for this message
Alessandro Ghedini (ghedo) wrote :

What program were you running under valgrind? Also, it looks very similar to https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/332496

Revision history for this message
David Kastrup (dak) wrote :

This bug is more than a year ago. I would think it most likely that I was working on some self-compiled version of LilyPond (it is a C++/Guile combination, where Guile is a Scheme interpreter using a conservative garbage collector).

I don't think that the debugged binary was overly relevant in the crash, however. But I can't tell anything for sure anymore: it has been far too long.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.