Am 16.10.14 04:06, schrieb Andrew Piskorski:
> Good idea. The automatic bisect didn't give me the answer, but it did
> get me started down a useful path. The culprit with nsthreadtest
> seems to be, Tcl 8.5!
That's would have been my first guess, since (a) nsthreadtest is not in
regular use,
and
On Wed, Oct 15, 2014 at 10:06:48PM -0400, Andrew Piskorski wrote:
> All that seems to matter, is that nsthreadtest ALWAYS fails when I
> configured with this:
> --with-tcl=/usr/lib/tcl8.5
> And if I instead use Tcl 8.4 like this it works fine:
> --with-tcl=/usr/lib/tcl8.4
I Compared the confi
On Wed, Oct 15, 2014 at 10:24:19PM +0100, Stephen wrote:
> You have a known good revision: aolserver-4.0.10, a known bad: tip,
> and an automated test to distinguish between the two states:
> nsthreadtest. Try 'hg bisect ...' to figure out where the error was
> introduced.
Good idea. The automat
On Wed, Oct 15, 2014 at 8:24 PM, Andrew Piskorski wrote:
>
> On Wed, Oct 15, 2014 at 03:45:59AM -0400, Andrew Piskorski wrote:
>
> > In my own application on Windows, my connection thread tells a worker
> > thread to do something using nsv, mutexes, and a condition variable.
> >
> > This is old co
On Wed, Oct 15, 2014 at 03:45:59AM -0400, Andrew Piskorski wrote:
> In my own application on Windows, my connection thread tells a worker
> thread to do something using nsv, mutexes, and a condition variable.
>
> This is old code that works fine on AOLserver 4.0.x (on a different
> older Windows
Is the stand-alone nsthreadtest program supposed to work?
It dumps core for me on both Windows and Linux.
In my own application on Windows, my connection thread tells a worker
thread to do something using nsv, mutexes, and a condition variable.
This is old code that works fine on AOLserver 4.0.x
