On Sun, 2003-01-05 at 08:04, Mika Liljeberg wrote:
Hi,
I have further information on the following bug:
http://bugzilla.ximian.com/show_bug.cgi?id=34164
Observed on Evo 1.2.0. I got this by selecting all messages in a vfolder
and trying to set a label on them.
I managed to trap this
Hi Jeff,
You'll note that EMsgPort has its own .lock member, which is acquired by
e_msgport_put(), e_msgport_get(), e_msgport_wait() and all other
routines before accessing or modifying the message port data. To me this
a pretty strong indication that this is a mailbox that is accessed by
On Sun, 2003-01-05 at 13:22, Mika Liljeberg wrote:
Hi Jeff,
You'll note that EMsgPort has its own .lock member
yes, I know :-)
, which is acquired by
e_msgport_put(), e_msgport_get(), e_msgport_wait() and all other
routines before accessing or modifying the message port data.
yea...
On Sun, 2003-01-05 at 20:30, Jeffrey Stedfast wrote:
What I'm saying is that EThread.server_port's queue is not modified
outside of a EThread.mutex and so it is all safe. If that wasn't the
case, I would agree with you - then there would be a poblem, but as far
as I can tell, EThread.mutex is
