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

[Carlo de Falco]

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

[comment #26 comment #26:]
> Could you please check the value of m_rep when lldb stops with the error
(see jwe's comment #12)?
> Write "p m_rep" at the lldb prompt and show the results. Is it a very low or
very high number?


Here it is :


Process 10441 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x1107b06e0)
    frame #0: 0x0000000105d9c2d1
liboctinterp.7.dylib`octave::graphics_toolkit::update(this=0x00007ffeeabccdc8,
go=0x00007ffeeabcce60, id=20) at graphics-toolkit.h:241:14
   238      // Notifies graphics toolkit that object't property has changed.
   239      void update (const graphics_object& go, int id)
   240      {
-> 241        m_rep->update (go, id);
   242      }
   243  
   244      void update (const graphics_handle& h, int id)
Target 0: (octave-cli) stopped.
(lldb) p m_rep
(std::__1::shared_ptr<octave::base_graphics_toolkit>) $0 =
std::__1::shared_ptr<octave::base_graphics_toolkit>::element_type @
0x00007f813de27cf0 strong=3 weak=1 {
  __ptr_ = 0x00007f813de27cf0
}
(lldb) 



    _______________________________________________________

Reply to this item at:

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

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