[Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot

[Carlo de Falco]

Follow-up Comment #29, bug #57245 (project octave):

[comment #28 comment #28:]


> This time, the access error occurred in a different function than in the
other backtraces.

sorry that is because I triggered the segfault with a different
sequence of commands, i.e. "plot (randn (5)); clear all; plot (randn (5))"

This is instead what I get with the same commands as in comment #23 :


Process 26762 resuming
Process 26762 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x11a9bd6e8)
    frame #0: 0x000000011001889b
liboctinterp.7.dylib`octave::graphics_toolkit::initialize(this=0x00007ffee094ce90,
go=0x00007ffee094cf18) at graphics-toolkit.h:252:21
   249      // Notifies graphics toolkit that new object was created.
   250      bool initialize (const graphics_object& go)
   251      {
-> 252        return m_rep->initialize (go);
   253      }
   254  
   255      bool initialize (const graphics_handle& h)
Target 0: (octave-cli) stopped.


and here is the result for inspecting the variables :


(lldb) p m_rep
(std::__1::shared_ptr<octave::base_graphics_toolkit>) $0 =
std::__1::shared_ptr<octave::base_graphics_toolkit>::element_type @
0x00007fc93b785fe0 strong=3 weak=1 {
  __ptr_ = 0x00007fc93b785fe0
}
(lldb) p go
(const graphics_object) $1 = {
  rep = std::__1::shared_ptr<base_graphics_object>::element_type @
0x00007fc93d00f600 strong=2 weak=1 {
    __ptr_ = 0x00007fc93d00f600
  }
}
(lldb) 


    _______________________________________________________

Reply to this item at:

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

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