[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 84303] New: How about a LockCheck tool?
From:       Howard Chu <hyc () symas ! com>
Date:       2004-07-01 10:10:12
Message-ID: 20040701101012.31618.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=84303      
           Summary: How about a LockCheck tool?
           Product: valgrind
           Version: 2.1.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: jseward acm org
        ReportedBy: hyc symas com


Version:           2.1.0 (using KDE KDE 3.2.1KDE 1.2)
Installed from:    Compiled From SourcesCompiled From Sources
Compiler:          gcc 3.3.4 
OS:                Linux

I'm trying to chase down some deadlocks in a multithreaded program. Helgrind isn't \
helping, because it doesn't seem to recognize all of the locks that this program \
uses. (E.g., using our own implementation of read/writer locks, protected by standard \
mutexes.)

What would be nice is something like memcheck that, instead of tracking malloc/free, \
tracks lock/unlock, recording the thread and stack context of each locking event. It \
would probably be prohibitively expensive to add deadlock detection to the mix, but \
at least having a record would allow diagnosis after it's become obvious that a \
deadlock has occurred.

I'm not sure if this should be an extension of an existing tool, or all by itself. As \
a side note, sometimes my program runs off into free'd memory instead of deadlocking, \
and those times I wish I had the memcheck skin available to catch it.


[prev in list] [next in list] [prev in thread] [next in thread]