This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: NPTL thread support
H. J. Lu writes:
> On Mon, May 12, 2003 at 03:20:13PM -0400, J. Johnston wrote:
> > H.J.,
> >
> > Can you confirm that configuration set HAVE_TKILL_SYSCALL to 1
> > in config.h? Can you also confirm that the value: tkill_failed in
> > lin-lwp.c is not set to true when running the debugger?
> >
>
> It was a pilot error. The "make check" hang is gone. Here are the
> failures in today's cvs on RedHat 9.
thanks, that's more reasonable.
(I still have a rewrite of the TLS tests to resubmit...)
elena
>
> H.J.
> ----
> FAIL: gdb.asm/asm-source.exp: x/i globalvar (memory read error)
> FAIL: gdb.base/selftest.exp: step into xmalloc call
> FAIL: gdb.java/jmisc.exp: setting breakpoint at jmisc.main
> FAIL: gdb.java/jmisc.exp: ptype jmisc
> FAIL: gdb.java/jmisc.exp: p args
> FAIL: gdb.java/jmisc.exp: p *args
> FAIL: gdb.java/jmisc1.exp: ptype jmisc
> FAIL: gdb.java/jmisc2.exp: ptype jmisc
> FAIL: gdb.mi/mi-var-display.exp: get children local variable weird
> FAIL: gdb.mi/mi1-var-display.exp: get children local variable weird
> FAIL: gdb.objc/basicclass.exp: breakpoint method
> FAIL: gdb.objc/basicclass.exp: breakpoint method with colon
> FAIL: gdb.objc/basicclass.exp: breakpoint class method with colon
> FAIL: gdb.objc/basicclass.exp: continue until method breakpoint
> FAIL: gdb.objc/basicclass.exp: resetting breakpoints when rerunning
> FAIL: gdb.objc/basicclass.exp: continue until method breakpoint
> FAIL: gdb.objc/basicclass.exp: print an ivar of self
> FAIL: gdb.objc/basicclass.exp: print self
> FAIL: gdb.objc/basicclass.exp: print contents of self
> FAIL: gdb.objc/basicclass.exp: breakpoint in category method
> FAIL: gdb.objc/basicclass.exp: continue until category method
> FAIL: gdb.objc/basicclass.exp: Call an Objective-C method with no arguments
> FAIL: gdb.objc/basicclass.exp: Call an Objective-C method with one argument
> FAIL: gdb.objc/basicclass.exp: Use of the print-object command
> FAIL: gdb.objc/basicclass.exp: Use of the po (print-object) command
> FAIL: gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily (timeout)