octave-maintainers
[Top][All Lists]
Advanced

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

Re: Weird behavior with mislocked: oct-file is unloaded while checking l


From: Michael Goffioul
Subject: Re: Weird behavior with mislocked: oct-file is unloaded while checking lock state...
Date: Thu, 4 Sep 2008 16:40:35 +0200

On Thu, Sep 4, 2008 at 4:16 PM, John W. Eaton <address@hidden> wrote:
> The mislocked function calls symbol_table::find_function, which should
> eventually call symbol_table::fcn_info::fcn_info_rep::find.  Can you
> step through that function (and the functions it calls) and find out
> where it is that fltk_backend.oct is unmapped?

starting from symbol_table::fcn_info::fcn_info_rep::find, the
call sequence is the following:

find_autoload: symtab.cc: 624
out_of_date_check_internal: symtab.cc: 704
function = octave_value (): symtab.cc: 209

Note that this only happen with an autoloaded function
(in this case, __init_fltk__). If I do

mislocked ('fltk_backend')

the oct-file is not unmapped.

Michael.


reply via email to

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