Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jun 1998 15:14:32 -0700 (PDT)
From:      Tom <tom@uniserve.com>
To:        John Birrell <jb@cimlogic.com.au>
Cc:        edmond@shaman.lycaeum.org, stable@FreeBSD.ORG, monty@tcx.se
Subject:   Re: is libc_r broken in 980520-SNAP (and stable?)?
Message-ID:  <Pine.BSF.3.96.980617150342.4669F-100000@shell.uniserve.ca>
In-Reply-To: <199806172155.HAA12635@cimlogic.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help

On Thu, 18 Jun 1998, John Birrell wrote:

> The version of libc_r in the RELENG_2_2 contains fixes for all bugs that
> people have reported. In Highwind's case, they have code that did things
> like read/write with zero bytes; and write to a read only file. These
> caused libc_r to hang waiting on a file descriptor to become ready when
> it never would. Most software doesn't do this sort of thing. It seems
> to come from C++ code. 8-)

  Are you aware of the problems with MySQL?  I have 2.2.6-stable of May
21, and a signal/alarm test program (thr_alarm) hangs.

  Also, how should -stable threaded applications be compiled and linked?
You mentioned before that "-pthread" should be used rather than linking
with libc_r?  Does that apply to -stable too?  I think -stable thread apps
need to be compiled with "-D_THREAD_SAFE" and linked with "-lc_r" but I'm
not sure anymore.

> -- 
> John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
> CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137

Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980617150342.4669F-100000>