octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #44387] unwind_protect_cleanup apparently fail


From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #44387] unwind_protect_cleanup apparently fails to run when calling graphics C++ code
Date: Sat, 04 Apr 2015 10:21:14 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0

Follow-up Comment #8, bug #44387 (project octave):

As explained in bug #44463, I could check that the gh_manager::lock/unlock
mechanism doesn't seem to work. As I understand it should work as a cross
thread mutex.

I attached a diff in which I tried to follow who lock and unlock the
gh_manager: I don't know if I should trust the order in which the callers are
printed on screen (due to possible threading issues) but here is the result I
see in the terminal when I paste Rick's script:


>> close all
>> surf (peaks)
>> get (gcf, "color")
ans =

   1   1   1

>> print -dfoo tst.eps
drawnow unlocked the mutex
drawnow locked the mutex
>> get Canvas::print locked the mutex
Unknown device: foo
Unrecoverable error: undefined in .uninstallpagedevice
Operand stack:
    defaultdevice
              Canvas::print unlocked the mutex
  

In normal operation I would expected something like:


>> print -dfoo tst.eps
drawnow unlocked the mutex
Canvas::print locked the mutex
Canvas::print unlocked the mutex
drawnow locked the mutex
>>               
  


(file #33531)
    _______________________________________________________

Additional Item Attachment:

File name: gh_manager_lock.diff           Size:2 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44387>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/




reply via email to

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