[Top][All Lists]

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

[Octave-bug-tracker] [bug #55143] pkg install only succeeds on second at

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #55143] pkg install only succeeds on second attempt (Windows only)
Date: Sat, 1 Dec 2018 17:11:48 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Update of bug #55143 (project octave):

                  Status:               Need Info => Confirmed              


Follow-up Comment #5:

Thanks Hartmut for testing.

The issue is undoubtedly that in Windows, unlike Linux (Mac OSX I don't know),
the binary module files of a package (the .oct files) are locked as long as
their symbols are in the symbol table (or some other place in Octave where the
"connections" to those functions are kept).
I suspect that binary functions get locked as soon as the subdir containing
those functions is added to the path during loading of the package.

It just occurred to me that a plain "clear -f" might also wipe functions
entered on the command line. So pkg.m needs to be able to find out exactly
which functions have been loaded by a specific package in order to clear only
those upon unloading the package.
That might complicate matters a little.

I had a brief look in pkg.m and .../<pkg>/private/unload_packages.m; my
conclusion is that ATM I have no time to delve sufficiently deep into it.
Moreover, I don't know the intricacies of loading binary OF package modules.

I'll add JWE to the cc list, I suppose he knows in detail how the mechanism of
loading binary modules works. If he has a good hint I may pick up somewhere
the next weeks, if no one else beats me to it.

Status -> Confirmed


Reply to this item at:


  Message sent via Savannah

reply via email to

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