> > Next, please try compiling and running the attached file. It works
> > for me, but meebey claims that it fails for him under gnome-session
> > (but not on the console). You can compile it with 'mcs', as in:
> > 
> >         mcs thread_abort.cs
> >         ./thread_abort.exe
> 
> Works under GNOME (started in gnome-terminal 2.18.4-1):
> 
> $ ./thread_abort.exe
> mono_thread_get_abort_signal(): 36
> thread.Start()
> Worker(): thread started
> Worker(): working... 0
> Worker(): working... 1
> Worker(): working... 2
> Worker(): working... 3
> Worker(): working... 4
> thread.Abort()
> press enter to quit!
> Worker(): working... 5
> Worker(): working... 6
> $
> 
> Best,
> André

It doesn't work you for, the thread is continuing after it trying to
abort it. This how it should like:

[EMAIL PROTECTED]:~/sigblg-mask-issue$ ./test-thread-abort.exe 
thread.Start()
Worker(): thread started
Worker(): working... 0
Worker(): working... 1
Worker(): working... 2
Worker(): working... 3
Worker(): working... 4
thread.Abort()
press enter to quit!
Worker(): thread aborted!
Worker(): thread ended

notice the "thread aborted" line which misses in your case.

So you suffer from the same threading issue that happened for me!
The good news is, I could track down the cause up to gnupg-agent, and
this issue is fixed since gnupg-agent 2.0.9-3.1

For full background of this issue see: #499569

Can you confirm that this issue doesn't happen anymore with f-spot for
you (I am just assuming you are using gpg-agent)? Then we can
close this bugreport.

PS: I would have replied earlier about my findings with the threading
issue if I would have seen your output (I passed the thread_abort.cs
code to Tim), but [EMAIL PROTECTED] was used and thus I had
no chance...

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    [EMAIL PROTECTED]  http://www.meebey.net/
PEAR Developer    [EMAIL PROTECTED]     http://pear.php.net/
Debian Developer  [EMAIL PROTECTED]  http://www.debian.org/



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to