bug-commoncpp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: differences between getThread () on unices and win32


From: David Sugar
Subject: Re: differences between getThread () on unices and win32
Date: Wed, 20 Feb 2002 07:38:10 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914

Freddy, do you think this issue is still in the 2 tree? I recall this was changed around a bit...

Pavel Tsekov wrote:

Hello, there! :)

getThread () on Win32 seem to not follow the trend and looks a
little bit outdated. It uses the old implementation - its the same
as in 1.6.x perhaps even before that. Would a patch be required to
add this functionality or not ? I would vote for simply copying the
unix implementation without the fix for Solaris... Is this acceptable
? If a a patch is required I'd supply one...

For the curious I've found this difference because of SEGV caused
by getException () which calls getThread () to retrieve the _throw
thread artifact on a thread other than the main one. Now I am curios
is it acceptable to remove the _throw member from thread and make it
a thread data ? This involves patching get/setException... Please, let
me know - I am willing to provide the patches - just want to know
if there are any pros / cons on this topic. I think a common situation
where this will be a better solution is applications which do not use
CommonC++ for their threading purposes.

Thanks :)


_______________________________________________
Bug-commoncpp mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/bug-commoncpp






reply via email to

[Prev in Thread] Current Thread [Next in Thread]