Re: Weird behavior with mislocked: oct-file is unloaded while checking lock state...

[John W. Eaton]

On  4-Sep-2008, Michael Goffioul wrote:

| 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.

OK, so what is the value of nm in out_of_date_check_internal?

I guess in the case of autoloaded files, we should be looking at the
name of the file that contains the autoloaded function, though I'm not
sure precisely what change to make at the moment that won't break some
other case.

jwe