|
From: | Ian Journeaux |
Subject: | [Octave-bug-tracker] [bug #41699] imread causes a segmentation fault when exiting Octave |
Date: | Wed, 04 Jun 2014 05:15:43 +0000 |
User-agent: | Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 |
Follow-up Comment #39, bug #41699 (project octave): I stepped up the backtrace. When doing that I found this in the source. The back trace goes though line 236 which is symbol_table::erase_scope (local_scope); which has a "// FIXME: this is really playing with fire." comment. 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); } _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?41699> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |