octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Segmentation Fault with Octave MXE under Windows


From: Carnë Draug
Subject: Re: Segmentation Fault with Octave MXE under Windows
Date: Wed, 4 Jun 2014 17:16:46 +0100

On 4 June 2014 17:09, Daniel J Sebald <address@hidden> wrote:
> On 06/04/2014 04:31 AM, ijourneaux wrote:
>>
>> 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?
>
>
> Not sure.  local_scope is assigned the value "sid" which is passed into the
> routine.  If the procedure is that octave_user_function assumes control and
> cleanup of the function table for that scope, then it's fine.  But if some
> other part of the code is still using those parts of the function table then
> it is a problem.  Cleanup should be done elsewhere.  erase_scope() in
> symtab.h ensures the scope is local.

The following may be complete rubbish or related if there's something
related to scope of functions: imformats keeps a persistent struct
with function handles for the private functions within
"m/image/private". This is created during the first call to one of the
image IO functions (imwrite, imread, and imfinfo).

Carnë



reply via email to

[Prev in Thread] Current Thread [Next in Thread]