memcheck crashed with SIGSEGV in do_syscall_WRK()

Bug #150477 reported by JohnRett
72
This bug affects 8 people
Affects Status Importance Assigned to Milestone
valgrind (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: valgrind

I was debugging a leaky program.

==13919== Rerun with --leak-check=full to see details of leaked memory.
Segmentation fault (core dumped)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Oct 8 03:57:19 2007
Dependencies:
 libgcc1 1:4.2.1-5ubuntu4
 gcc-4.2-base 4.2.1-5ubuntu4
 libc6 2.6.1-1ubuntu9
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/valgrind/x86-linux/memcheck
NonfreeKernelModules: cdrom
Package: valgrind 1:3.2.3-2ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/bin/valgrind.bin ./rescue281 -q -i ./tests/first.txt
ProcCwd: /home/bagside/eecs281/pa1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/bagside/local/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: valgrind
Stacktrace:
 #0 0x38026582 in do_syscall_WRK () at m_syscall.c:56
 No locals.
StacktraceTop: do_syscall_WRK () at m_syscall.c:56
ThreadStacktrace:
 .
 Thread 1 (process 13919):
 #0 0x38026582 in do_syscall_WRK () at m_syscall.c:56
 No locals.
Title: memcheck crashed with SIGSEGV in do_syscall_WRK()
Uname: Linux bvapp 2.6.22-13-386 #1 Thu Oct 4 16:50:05 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

SegvAnalysis:
 Segfault happened at: 0x38026582 <do_syscall_WRK+34>: pop %ebp
 PC (0x38026582) ok
 source "%ebp" ok
 destination "(%esp)" (0x625487c4) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x625487c4) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
JohnRett (jrett) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:do_syscall_WRK () at m_syscall.c:56

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in valgrind:
importance: Undecided → Medium
Connor Imes (ckimes)
visibility: private → public
Kees Cook (kees)
description: updated
Revision history for this message
Loïc Minier (lool) wrote :

Could you please recheck with valgrind 3.6.0 in Ubuntu 10.04 LTS beta?

Revision history for this message
Stef Walter (stefw) wrote :

I'm away from my office for the near term, and unable to reproduce this on my laptop. Sorry about that.

Revision history for this message
Loïc Minier (lool) wrote :

No problem, I'm marking the bug as Incomplete for now, but please reopen when you get the chance to reproduce.

Changed in valgrind (Ubuntu):
status: New → Incomplete
Kees Cook (kees)
description: updated
tags: added: stack-exhaustion
Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported should be reproducible with the live environment of the Desktop CD development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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".

Changed in valgrind (Ubuntu):
status: Incomplete → Invalid
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.