On Sunday 03 June 2012, Steven Chamberlain wrote:
> On 02/06/12 23:03, Stefan Fritsch wrote:
> > You have to run testlock, not testsock.
>
> Uhh, typo.
>
> testlock 'succeeds', but with this message, shown every time?
>
> > testlock: \Tim
On Saturday 02 June 2012, Steven Chamberlain wrote:
> On 02/06/12 20:42, Stefan Fritsch wrote:
> > I will just wait for an eglibc update and then see if it fixes
> > the problem.
>
> I tested this on my kfreebsd-i386 system where I already rebuilt
> eglibc
>
> w
On Sat, 2 Jun 2012, Steven Chamberlain wrote:
On 02/06/12 20:16, Stefan Fritsch wrote:
since recently, I get some test failure in apr on kfreebsd-i386 that
seem to indicate a bug in the kernel or libc. The failing test is part
of testlock.c and basically does a pthread_cond_timedwait
Hi,
since recently, I get some test failure in apr on kfreebsd-i386 that seem
to indicate a bug in the kernel or libc. The failing test is part of
testlock.c and basically does a pthread_cond_timedwait() with 5 second
timeout and measures that it returns no later than 5.1 seconds after the
c
Package: kfreebsd-5
Severity: grave
Tags: security
Justification: user security hole
Some security issues have been found in FreeBSD that probably affect
the Debian FreeBSD kernel:
CVE-2006-4304:
Buffer overflow in the sppp driver in FreeBSD 4.11 through 6.1, NetBSD
2.0 through 4.0 beta before
5 matches
Mail list logo
