[Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang)

[John W. Eaton]

Follow-up Comment #44, bug #57591 (project octave):

Yes, we are storing the graphics_object and it uses a shared_ptr to hold the
base_graphics_object that contains the actual data.  But it does not provide
copy-on-write semantics, so although the interpreter thread won't delete the
underlying base_graphics_object while the GUI thread holds the reference, it
can still change the contents unexpectedly while we are doing something with
the data unless we are locking correctly.

I don't know for sure that is the problem here.  Can we guarantee that we are
getting the locking right?  To me, that seems harder than implementing
copy-on-write semantics for objects, but I'm also not sure what is appropriate
for these objects.

Also, if the real problem in this case is a crash in Mesa, then are there
difference in versions between the systems where the crashes happen frequently
vs. those where it is rare (or maybe never happens?)

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57591>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/