From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "J. Johnston" <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFC: nptl threading patch for linux
Date: Sat, 10 May 2003 00:58:00 -0000 [thread overview]
Message-ID: <20030510005832.GB32695@nevyn.them.org> (raw)
In-Reply-To: <3EBC2D6D.70001@redhat.com>
On Fri, May 09, 2003 at 06:36:29PM -0400, Andrew Cagney wrote:
> >On Thu, Apr 24, 2003 at 04:52:04PM -0400, J. Johnston wrote:
> >
> >>The following is the last part of my revised nptl patch that has
> >>been broken up per Daniel J.'s suggestion. There are no generated
> >>files included in the patch.
> >
> >
> >Well, this patch doesn't work for me :( Using 2.5.69, since I don't
> >have any of the Red Hat kernels available here at the moment. It looks
> >like GDB bellies up around the second thread creation.
>
> Hmm, I've a horrible feeling that people are going to get bogged down
> trying to sort out which GLIBC and Kernel they should all use.
>
> Is there a list of Kernel and GLIBC fixes that are needed?
I'm just using the most recent releases of NPTL and the Linux kernel,
and the glibc CVS snapshot associated with that release of NPTL. Today
it's 2.5.69-bk and 0.37.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-10 0:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 22:05 J. Johnston
2003-05-09 22:00 ` Daniel Jacobowitz
2003-05-09 22:36 ` Andrew Cagney
2003-05-10 0:58 ` Daniel Jacobowitz [this message]
2003-05-09 23:38 ` J. Johnston
2003-05-10 0:58 ` Daniel Jacobowitz
2003-05-10 21:18 ` Daniel Jacobowitz
2003-05-10 21:59 ` Daniel Jacobowitz
2003-05-12 19:36 ` J. Johnston
2003-08-17 20:49 ` Daniel Jacobowitz
2003-06-02 18:49 ` Michael Snyder
2003-06-04 20:52 ` J. Johnston
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=20030510005832.GB32695@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.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