Date: Wed, 14 Jul 2004 00:44:04 +1000 From: Emil Mikulic <g3c7a531@dmr.ath.cx> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/68992: valgrind stuck in umtx state before exit Message-ID: <20040713144404.GA24997@dmr.ath.cx> Resent-Message-ID: <200407131450.i6DEoLZb099918@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 68992 >Category: kern >Synopsis: valgrind stuck in umtx state before exit >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 13 14:50:20 GMT 2004 >Closed-Date: >Last-Modified: >Originator: >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: System: FreeBSD beastie.home 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Tue Jul 13 23:10:20 EST 2004 root@beastie.home:/usr/obj/usr/src/sys/PANTSU i386 >Description: I'm inclined to think this is a bug in the kernel rather than valgrind because this wasn't happening with a kernel from a few weeks ago. I'm running a 5-CURRENT world and kernel as of 13 July 2004 at 12:40 UTC. valgrind hangs before exit, after printing leak information. top says it's stuck in the umtx state: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 516 emikulic 95 0 335M 7176K umtx 0:00 0.00% 0.00% valgrind DDB's ps says: pid proc uarea uid ppid pgrp flag stat wmesg wchan cmd 516 c18928ac d83f0000 1000 458 516 0004002 [SLPQ umtx 0xc17fa000][SLP] valgrind I can't kill it with SIGTERM, SIGINT, or SIGQUIT, and I can't suspend it. It dies on SIGKILL though. I get the same behaviour with both valgrind-327 and valgrind-snapshot-337. >How-To-Repeat: valgrind --tool=memcheck ls >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040713144404.GA24997>