Date: Tue, 13 Oct 1998 18:36:10 -0400 (EDT) From: HighWind Software Information <info@highwind.com> To: jb@cimlogic.com.au Cc: jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: Recent 3.0's are Depressing Message-ID: <199810132236.SAA07644@highwind.com> In-Reply-To: <199810132222.IAA05402@cimlogic.com.au> (message from John Birrell on Wed, 14 Oct 1998 08:22:24 %2B1000 (EST))
next in thread | previous in thread | raw e-mail | index | archive | help
HighWind Software Information wrote: > Hmm. Wouldn't statically linking OUR local libc_r into the application > make it so the changes to libc_r at the customer site not effect us? > Maybe I am missing something. Ah, sorry. Yes _customer_ site changes would be ruled out by that. I thought you were meaning your development system. Are you saying that you can't duplicate the customer's problem on your system? That is correct. It works like a charm at our site. At 2 different customer sites (both running recent 3.0's), it gets into this problem. At customers running older 3.0 SNAPSHOT's, it works fine. Quite frustrating. Send the application a SIGINFO, then look in /tmp/uthread.dump. We'll get this. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810132236.SAA07644>