|
| From: | Sébastien Villemot |
| Subject: | [Octave-bug-tracker] [bug #59597] bogus result returned by mexCallMATLAB |
| Date: | Wed, 9 Dec 2020 02:28:41 -0500 (EST) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Follow-up Comment #20, bug #59597 (project octave):
[comment #19 commentaire #19 :]
> Taking a look into the perfect_foresight_problem.cc the
DynamicModelMatlabCaller is evaluated that it indeed calls
mexCallMATLABWithTrap in the OMP parallel region. Generally Octave interpreter
and specially 'mexCallMATLAB' and its memory manager aren't thread safe and
concurrent accesses possibly corrupt the mex memory manager.
No, this case won’t happen. mexCallMATLABWithTrap() is only called when
use_dll=false, in which case OMP is disabled.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59597>
_______________________________________________
Message posté via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |