[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57591] Segmentation faults when running the t
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang) |
Date: |
Thu, 25 Jun 2020 06:58:16 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0 |
Follow-up Comment #43, bug #57591 (project octave):
@John: The GUI Object (a Figure here) already stores a reference to the
underlying graphics_object, see this excerpt from Object.h:
// Store the graphics object directly so that it will exist when
// we need it. Previously, it was possible for the graphics
// toolkit to get a handle to a figure, then have the interpreter
// thread delete the corresponding object before the graphics
// toolkit (GUI) thread had a chance to display it. It should be OK
// to store this object and use it in both threads (graphics_object
// uses a std::shared_ptr) provided that we protect access with
// mutex locks.
graphics_object m_go;
After this addition, we should have changed all the logic and removed m_handle
since m_go lets us access the object directly.
Anyway, is it me or what we see in the backtrace is a crash in Mesa, not in
Octave?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57591>
_______________________________________________
Message posté via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), (continued)
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Markus Mützel, 2020/06/03
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Markus Mützel, 2020/06/04
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), John W. Eaton, 2020/06/04
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Markus Mützel, 2020/06/07
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Markus Mützel, 2020/06/10
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Dmitri A. Sergatskov, 2020/06/10
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Hg200, 2020/06/10
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), John W. Eaton, 2020/06/11
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Markus Mützel, 2020/06/20
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), John W. Eaton, 2020/06/24
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang),
Pantxo Diribarne <=
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), John W. Eaton, 2020/06/25
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), John W. Eaton, 2020/06/26
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Dmitri A. Sergatskov, 2020/06/26
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), John W. Eaton, 2020/06/26
- [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang), Dmitri A. Sergatskov, 2020/06/26