This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFC: nptl threading patch for linux


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]