Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "J. Johnston" <jjohnstn@redhat.com>,
	gdb-patches@sources.redhat.com, roland@redhat.com
Subject: Re: RFC: nptl threading patch for linux
Date: Sat, 10 May 2003 21:18:00 -0000	[thread overview]
Message-ID: <20030510211855.GA4312@nevyn.them.org> (raw)
In-Reply-To: <20030509220011.GA22383@nevyn.them.org>

On Fri, May 09, 2003 at 06:00:11PM -0400, Daniel Jacobowitz 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.

Sorry, I found the problem.  Configure was not finding tkill.  Entirely
a local problem; but how would you feel about something which set the
default number for __NR_tkill if __i386__?  Or has someone already
discouraged that approach?

So:

>   - stop_wait_callback should be fixed to not be so dumb when this
>     happens.

This one is still true.  Patch for another day.

>   - we need to figure out how we got into this mess.
>   - and why the SIGSTOP never showed up.

But these are resolved.


I now get fairly good test results with your patch and NPTL; there are
some failures because of the vsyscall issue being currently discussed. 
Backtraces in linux-dp don't work because the threads are stopped in
the kernel page.

I can also report that the kernel change I am testing to report thread
exits does not appear to cause your patch any problems.  Yay!  More on
that in a little while.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2003-05-10 21:18 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
2003-05-09 23:38   ` J. Johnston
2003-05-10  0:58     ` Daniel Jacobowitz
2003-05-10 21:18   ` Daniel Jacobowitz [this message]
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=20030510211855.GA4312@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.com \
    --cc=roland@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