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

Bug #861186 reported by Till Kamppeter
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
valgrind (Ubuntu)
New
Undecided
Unassigned

Bug Description

Running CUPS under valgrind to fix a crasher, bug 855445, as asked for in comment #14 of that bug. Run command line

$ sudo -s
# valgrind -v --trace-children=yes /usr/bin/cupsd -f > /tmp/log 2>&1

and from another terminal applying the tortures of comment #9 of the mentioned bug to CUPS. Crashed in the middle of the execution to create the queues, but CUPS kept running and all queues got created.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: valgrind 1:3.6.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Wed Sep 28 08:35:21 2011
ExecutablePath: /usr/lib/valgrind/memcheck-amd64-linux
ProcCmdline: valgrind.bin -v --trace-children=yes /usr/lib/cups/backend/usb
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF8
Signal: 11
SourcePackage: valgrind
StacktraceTop:
 do_syscall_WRK ()
 vgPlain_do_syscall (sysno=<optimized out>, a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=0, a7=0, a8=0) at m_syscall.c:739
 vgPlain_kill (pid=<optimized out>, signo=<optimized out>) at m_libcsignal.c:304
 vgPlain_kill_self (sigNo=11) at m_signals.c:1392
 shutdown_actions_NORETURN (tid=<optimized out>, tids_schedretcode=VgSrc_FatalSig) at m_main.c:2482
Title: memcheck-amd64-linux crashed with SIGSEGV in do_syscall_WRK()
UpgradeStatus: Upgraded to oneiric on 2009-12-18 (648 days ago)
UserGroups:

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #857676, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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