Re: Segmentation Fault with Octave MXE under Windows

[ijourneaux]

This is the bug report associated with this topic.

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

I tried navigating up the backtrace to see where the problem was
originating. The segfault goes through

symbol_table::erase_scope (local_scope); 

which has a "// FIXME: this is really playing with fire." at line 236. 
Useful info or just a red herring? 


octave_user_function::~octave_user_function (void) 
{ 
if (cmd_list) 
cmd_list->remove_all_breakpoints (file_name); 
delete param_list; 
delete ret_list; 
delete cmd_list; 
delete lead_comm; 
delete trail_comm; 
#ifdef HAVE_LLVM 
delete jit_info; 
#endif 
// FIXME: this is really playing with fire. 
symbol_table::erase_scope (local_scope);    //Line 236
}



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Segmentation-Fault-with-Octave-MXE-under-Windows-tp4664305p4664453.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.