[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run
From: |
Carlo de Falco |
Subject: |
[Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot |
Date: |
Sun, 15 Dec 2019 04:57:39 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0 |
Follow-up Comment #32, bug #57245 (project octave):
[comment #28 comment #28:]
> Could you please try if you still see the error with the attached patch
(with little hope it will fix anything)?
>
> (file #48060)
Here's the result of running with your patch applied :
frame #0: 0x000000010ba2d89b
liboctinterp.7.dylib`octave::graphics_toolkit::initialize(this=0x00007ffee4f33e90,
go=0x00007ffee4f33f18) 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)
(lldb) up
frame #1: 0x000000010b9d178d
liboctinterp.7.dylib`base_graphics_object::initialize(this=0x00007fa93386da00,
go=0x00007ffee4f33f18) at graphics.h:2886:27
2883 if (! toolkit_flag)
2884 {
2885 octave::graphics_toolkit tk = get_toolkit ();
-> 2886 toolkit_flag = tk.initialize (go);
2887 }
2888 }
2889
(lldb) down
frame #0: 0x000000010ba2d89b
liboctinterp.7.dylib`octave::graphics_toolkit::initialize(this=0x00007ffee4f33e90,
go=0x00007ffee4f33f18) 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)
(lldb) p m_rep
(std::__1::shared_ptr<octave::base_graphics_toolkit>) $0 =
std::__1::shared_ptr<octave::base_graphics_toolkit>::element_type @
0x00007fa9358d1d20 strong=3 weak=1 {
__ptr_ = 0x00007fa9358d1d20
}
(lldb) p go
(const graphics_object) $1 = {
rep = std::__1::shared_ptr<base_graphics_object>::element_type @
0x00007fa93386da00 strong=2 weak=1 {
__ptr_ = 0x00007fa93386da00
}
}
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57245>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Carlo de Falco, 2019/12/13
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Markus Mützel, 2019/12/13
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Carlo de Falco, 2019/12/14
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Markus Mützel, 2019/12/14
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Carlo de Falco, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Carlo de Falco, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Markus Mützel, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot,
Carlo de Falco <=
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Carlo de Falco, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Markus Mützel, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "clear all" generates segfault if run before or after a plot, Markus Mützel, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, Markus Mützel, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, Carlo de Falco, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, Carlo de Falco, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, Markus Mützel, 2019/12/15
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, John W. Eaton, 2019/12/16
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, John W. Eaton, 2019/12/16
- [Octave-bug-tracker] [bug #57245] "mlock" inside a compiled function locks the calling function instead, Carlo de Falco, 2019/12/16