From: Mark Kettenis <kettenis@science.uva.nl>
To: Michael Snyder <msnyder@cygnus.com>
Cc: Kevin Hise <kevinh@ridgecrest.ca.us>,
GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: Linux thread debugging patch?
Date: Tue, 13 Mar 2001 02:57:00 -0000 [thread overview]
Message-ID: <s3iae6qc50z.fsf@debye.wins.uva.nl> (raw)
In-Reply-To: <3AAD2530.D13A26CC@cygnus.com>
Michael Snyder <msnyder@cygnus.com> writes:
> Kevin Hise wrote:
> >
> > Is there a patch for 5.0 that corrects the problems debugging PThreads on
> > Linux?
>
> What problem debugging PThreads on Linux? I was pretty sure that was working in 5.0...
>
> Mark K? You out there?
I don't know if the capitalization of PThreads is significant here.
All I know is that GDB 5.0 supports LinuxThreads (which is the
standard pthreads implementation on Linux), but that support has a
couple of serious problems. I almost completely rewrote the stuff for
GDB 5.1. I don't think it is possible to create a patch for GDB 5.0.
So the only advice I can give Kevin is to get a recent snapshot, and
see if that works.
Mark
prev parent reply other threads:[~2001-03-13 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 23:13 Kevin Hise
2001-03-12 11:48 ` Michael Snyder
2001-03-13 2:57 ` Mark Kettenis [this message]
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=s3iae6qc50z.fsf@debye.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=kevinh@ridgecrest.ca.us \
--cc=msnyder@cygnus.com \
/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