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

List:       kde-bugs-dist
Subject:    [Bug 84348] New: Support linuxthreads_db?
From:       Howard Chu <hyc () symas ! com>
Date:       2004-07-02 7:19:22
Message-ID: 20040702071922.21606.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=84348      
           Summary: Support linuxthreads_db?
           Product: valgrind
           Version: 2.1.1
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: jseward acm org
        ReportedBy: hyc symas com


It would be nice if valgrind's thread library supported the debugger interface
so that when gdb is attached, you can get backtraces on all the client threads.

What would also be useful is a way to break into gdb at any arbitrary time, to
examine the client state. I added a User Request for this in my copy of valgrind
2.0.0 but the only way I could think of triggering it was via a signal handler.
When gdb attaches, the only stack I can see is that of the signal handler's,
which isn't very interesting.

I suppose you could accomplish this by preloading a custom libthread_db on the
gdb invocation, haven't looked into it in great detail.
[prev in list] [next in list] [prev in thread] [next in thread]