From: Daniel Jacobowitz <drow@mvista.com>
To: "Richard A. Painter" <r.painter@ieee.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb
Date: Tue, 30 Jul 2002 20:37:00 -0000 [thread overview]
Message-ID: <20020731033758.GA11828@nevyn.them.org> (raw)
In-Reply-To: <3D40B4CB.D569130A@ieee.org>
On Thu, Jul 25, 2002 at 08:32:43PM -0600, Richard A. Painter wrote:
> i was reviewing the documentation for gdb and found no references to pthreads
> specifically but did see some thread support.
>
> pthreads embodies threads, mutexes and condition variables. i saw no references
> to the mutexes and condition variables in the docs.
>
> does gdb support pthreads, mutexes and condition variables?
How would a debugger support mutexes and condition variables? They'll
still work in programs run under the debugger. Pthreads does not
expose convenient interfaces for examining their states, though.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-31 3:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 19:33 gdb Richard A. Painter
2002-07-30 20:37 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 7:05 Gdb Russell Shaw
2006-10-25 12:49 ` Gdb Daniel Jacobowitz
2006-10-25 13:38 ` Gdb Russell Shaw
2006-10-25 14:17 ` Gdb Daniel Jacobowitz
2006-10-25 16:29 ` Gdb Russell Shaw
2006-10-25 20:16 ` Gdb Eli Zaretskii
2006-10-25 20:08 ` Gdb Eli Zaretskii
2006-10-26 2:28 ` Gdb Russell Shaw
2006-10-26 7:11 ` Gdb Eli Zaretskii
2006-10-26 8:16 ` Gdb Russell Shaw
2006-10-26 20:01 ` Gdb Jim Blandy
2006-10-27 3:29 ` Gdb Russell Shaw
2002-05-29 13:06 gdb bemis
2002-03-22 7:18 gdb Kees Everaars
2002-03-26 17:04 ` gdb Michael Snyder
[not found] <20011117045052.5412.qmail@web13905.mail.yahoo.com>
2001-11-07 6:01 ` GDB Christopher Faylor
2001-02-27 9:14 gdb Mathieu Dube
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020731033758.GA11828@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=r.painter@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox