This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

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: new syscall stub support for ia64 libc

From: David Mosberger <davidm at napali dot hpl dot hp dot com>
To: drepper at redhat dot com, Jakub Jelinek <jakub at redhat dot com>,libc-hacker at sources dot redhat dot com
Date: Wed, 12 Nov 2003 23:31:59 -0800
Subject: Re: new syscall stub support for ia64 libc
References: <200310290426.h9T4Q9pw014305@napali.hpl.hp.com><20031029074436.GR12344@sunsite.ms.mff.cuni.cz><16288.50694.36460.339805@napali.hpl.hp.com><20031031084249.GA30446@twiddle.net><20031031070114.GV12344@sunsite.ms.mff.cuni.cz><16290.37282.439025.287911@napali.hpl.hp.com><20031031144724.GY12344@sunsite.ms.mff.cuni.cz><16306.47596.371542.356256@napali.hpl.hp.com>
Reply-to: davidm at hpl dot hp dot com

>>>>> On Wed, 12 Nov 2003 14:53:32 -0800, David Mosberger <davidm@linux.hpl.hp.com> said:


  David> - with nptl, make check shows failures in tst-cancel{6,9,17};
  David> I'll need to look into these as it's likely that I botched
  David> something in sysdep-cancel.h.

OK, I believe tst-cancel6 may be failing because cancellating the
victim thread fails to release the lock on the file that it's trying
to read from.  Is this test known to work for ia64 at all?  Is there a
good way to trace what's going on during cancellation?

	--david

Follow-Ups:
- Re: new syscall stub support for ia64 libc
  - From: Ulrich Drepper

References:
- Re: new syscall stub support for ia64 libc
  - From: David Mosberger

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