On Thu, Oct 08, 2009 at 02:10:28PM -0400, Charles Wilson wrote:
>Christopher Faylor wrote:
>> On Thu, Oct 08, 2009 at 01:37:34PM -0400, Charles Wilson wrote:
>>> Christopher Faylor wrote:
The version of insight that I built works fine for me on Windows XP SP3.
I just tried the sigint prob
Christopher Faylor wrote:
> On Thu, Oct 08, 2009 at 01:37:34PM -0400, Charles Wilson wrote:
>> Christopher Faylor wrote:
>>> The version of insight that I built works fine for me on Windows XP SP3.
>>> I just tried the sigint problem test case with it and it worked as
>>> expected.
>> OK. One more
On Thu, Oct 08, 2009 at 01:37:34PM -0400, Charles Wilson wrote:
>Christopher Faylor wrote:
>> The version of insight that I built works fine for me on Windows XP SP3.
>> I just tried the sigint problem test case with it and it worked as
>> expected.
>
>OK. One more try: here's an actual STC. It wor
Christopher Faylor wrote:
> The version of insight that I built works fine for me on Windows XP SP3.
> I just tried the sigint problem test case with it and it worked as
> expected.
OK. One more try: here's an actual STC. It works as expected if compiled
using:
1) gcc-3 -mno-cygwin -o thread_test
On Thu, Oct 08, 2009 at 12:18:35PM -0400, Charles Wilson wrote:
>Christopher Faylor wrote:
>>>This is coming up because any tcl app that I've built -- including
>>>insight -- always dies on exit, as tcl is shutting down its various
>>>utility threads.
>>
>>So why isn't this a problem with the curre
Christopher Faylor wrote:
> On Thu, Oct 08, 2009 at 07:18:49AM -0400, Charles Wilson wrote:
>> is it possible that cygwin
>> is overzealously inserting the _cygtls::call2() function into the return
>> frame stack? Does cygwin manipulate the TIB, even for threads created
>> by direct calls to Creat
On Thu, Oct 08, 2009 at 09:48:22AM -0400, Christopher Faylor wrote:
>Uh, yeah. If you are not using Cygwin methods to start threads then it
>is entirely likely that there will be problems, just like if you use
>non-Cygwin methods to do I/O.
OTOH, it is supposed to sort of work. That's what the c
Charles Wilson wrote:
> I have an idea why this is happening: I'm managing these threads
> manually using the windows API calls: CreateThread, WaitForSingleObject,
> SetEvent, etc. They are NOT actually started by cygwin's thread
> launching facilities (e.g. pthread).
Then you are doomed. Cyg
On Thu, Oct 08, 2009 at 07:18:49AM -0400, Charles Wilson wrote:
>I'm getting some weird crashes with threads. When a thread exits, I'm
>getting a SEGV in _cygtls::remove. That is, when the thread function
>returns, it ends up in cygtls::call2 (e.g. at B, below). Oddly, if I
>set a break point at
I'm getting some weird crashes with threads. When a thread exits, I'm
getting a SEGV in _cygtls::remove. That is, when the thread function
returns, it ends up in cygtls::call2 (e.g. at B, below). Oddly, if I
set a break point at A, it is never hit...
void
_cygtls::call2 (DWORD (*func) (void *,
10 matches
Mail list logo
