octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #55542] Undefined behavior in loading oct file


From: anonymous
Subject: [Octave-bug-tracker] [bug #55542] Undefined behavior in loading oct files and shared libraries
Date: Wed, 23 Jan 2019 01:04:07 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:60.9) Goanna/4.1 PaleMoon/28.2.0a1

Follow-up Comment #8, bug #55542 (project octave):

In oct-shlib.cc lines 379-380 for Windows the function "GetProcAddress" is
used:



function = reinterpret_cast<void *>

                   (GetProcAddress (h_libs[i], sym_name.c_str ()));


Readinging it's documentation
<https://docs.microsoft.com/en-us/windows/desktop/api/libloaderapi/nf-libloaderapi-getprocaddress>:



FARPROC GetProcAddress(
  HMODULE hModule,
  LPCSTR  lpProcName
);


It returns FARPROC that is a function pointer
<https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-callwindowproca>.

I think there is no problem with "void(*)()" or int(*)() because they can be
converted to any function pointer.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55542>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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