[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50463] gsvd implementation uses functions rem
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0 |
Date: |
Wed, 3 Jan 2018 09:53:11 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 |
Follow-up Comment #23, bug #50463 (project octave):
jwe: That is what I thought as well.
To change the dlsym-part of Octave's dynamic_library class shouldn't be too
hard.
Unfortunately, "GetModuleHandle (0)" only works for the "main" process.
Subsequent calls to "GetProcAddress" don't find functions linked in from
loaded libraries. I was unsuccessful finding an equivalent to RTLD_GLOBAL for
LoadLibrary (or GetModuleHandle).
Searching the loaded function list seems to be possible on HP/UX (but I have
no way of testing this). Removing support for it would also simplify the
code.
I haven't researched the DYLD_API (again, I have no way to test any changes).
If this could be removed as well even better (from a developer's point of
view).
I haven't tried. But for the Windows platform, it might be possible to query a
list of all loaded libraries (which are called "modules" in Microsoft's speech
from what I gather) with "EnumProcessModules" [1] on the current process and
then check each module iteratively with "GetProcAdress" for an entry point to
the queried function.
Should I give that a try?
[1]
https://msdn.microsoft.com/de-de/library/windows/desktop/ms682631(v=vs.85).aspx
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50463>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/02
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, John W. Eaton, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, John W. Eaton, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0,
Markus Mützel <=
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, John W. Eaton, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Carlo de Falco, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Carlo de Falco, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/03
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/07
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Carlo de Falco, 2018/01/22
- [Octave-bug-tracker] [bug #50463] gsvd implementation uses functions removed from lapack >= 3.6.0, Markus Mützel, 2018/01/23