Re: Cygwin port of Guile 2.2

2017-05-03 Thread Andy Wingo
On Wed 03 May 2017 05:18, Derek Upham writes: > Andy Wingo writes: > >> On Mon 01 May 2017 22:48, Derek Upham writes: >> >>> Running pthread_join() on a thread only guarantees that the thread has >>> returned an exit value. >> >> Would you mind providing a reference please? It is not that I do

Re: Cygwin port of Guile 2.2

2017-05-03 Thread szgyg
On Wed, May 03, 2017 at 11:24:30AM +0200, Andy Wingo wrote: > On Wed 03 May 2017 05:18, Derek Upham writes: > > > Andy Wingo writes: > > > >> On Mon 01 May 2017 22:48, Derek Upham writes: > >> > >>> Running pthread_join() on a thread only guarantees that the thread has > >>> returned an exit va

Re: Is the backtrace broken in 2.2.2?

2017-05-03 Thread Nala Ginrut
It always appears. Maybe relate to call-with-prompt? On Wed, May 3, 2017 at 3:45 AM, Andy Wingo wrote: > On Mon 01 May 2017 06:45, Nala Ginrut writes: > >> Hi all! >> I'm using the latest Guile from git repo. >> It seems something is wrong to print message of backtrace. >> >> ---

Re: Cygwin port of Guile 2.2

2017-05-03 Thread Derek Upham
Andy Wingo writes: > I think there's an argument that a thread doesn't "terminate" until its > thread-local key destructors have finished running, and therefore > pthread_join doesn't return until after the key destructors have run. > This is my understanding of what happens from reading NPTL. D

Re: Cygwin port of Guile 2.2

2017-05-03 Thread zv
On 05/02/2017 08:18 PM, Derek Upham wrote: > Andy Wingo writes: > >> On Mon 01 May 2017 22:48, Derek Upham writes: >> >>> Running pthread_join() on a thread only guarantees that the thread has >>> returned an exit value. >> >> Would you mind providing a reference please? It is not that I don't