bugGNU Octave - Bugs: bug #40824, newly compiled mex / oct function...

 
 

bug #40824: newly compiled mex / oct function in private subdirectory not detected

Submitted by:  Julien Bect <jbect>
Submitted on:  Fri 06 Dec 2013 12:36:01 PM UTC  
 
Category: InterpreterSeverity: 2 - Minor
Priority: 5 - NormalItem Group: Incorrect Result
Status: ConfirmedAssigned to: None
Originator Name: Open/Closed: Open
Release: devOperating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue 22 Aug 2017 06:38:20 PM UTC, comment #3:

It took quite a few tries to reproduce this, I thought this was about an existing function being recompiled. But this only affects a new function that has never been compiled before. To reproduce, the object files have to be deleted before Octave is started, then the compilation done while Octave is still running.

I can confirm this is still present when a dynamic mex or oct function is in a private directory on the load path.

One workaround that solves this is

which forces a complete reload of the load path, more brute-force than rehash, and the newly compiled private functions are found.

This is similar to bug #36230, in which new functions added to a class definition @-directory are not loaded once the class has already been parsed, until the path is altered or completely reloaded using the same workaround.

Mike Miller <mtmiller>
Project Administrator
Fri 25 Nov 2016 10:37:37 PM UTC, comment #2:

This might be connected to bug #40117 (m-files in private subfolder not found after changeing their timestamp).

Hartmut <hardy>
Sat 04 Jan 2014 05:31:40 AM UTC, comment #1:

I used a .oct file generated with mkoctfile, but the result is the same. The dynamic function in a private directory isn't seen until Octave is restarted.

Rik <rik5>
Project Administrator
Fri 06 Dec 2013 12:36:01 PM UTC, original submission:

If I compile a MEX file which is in a private folder, and the run a function from the parent folder, the compiled MEX file is not detected.

Julien Bect <jbect>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by mtmiller (Posted a comment)
  • -unavailable- added by hardy (Posted a comment)
  • -unavailable- added by rik5 (Posted a comment)
  • -unavailable- added by jbect (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 22 Aug 2017 06:38:20 PM UTCmtmillerSeverity3 - Normal=>2 - Minor
      SummaryMEX functions in private folders not detected after compilation=>newly compiled mex / oct function in private subdirectory not detected
    Sat 04 Jan 2014 05:31:40 AM UTCrik5StatusNone=>Confirmed

    Back to the top


    Powered by Savane 3.1-cleanup1