failed to find entry point even though Dependency Walker says it's there

Question

After launching my app, it complains that entry point glIsQuery could not be located. So I used Dependency Walker to debug this problem.

The Parent Import Function table does show that 'glIsQuery' is missing, as shown below

enter image description here

However, the Export Function List also shows that the symbol exists (I also used dumpbin to verify this) enter image description here

Any clue?

Clearly they are not the same name, the name decoration matters. — Hans Passant, Oct 25 '13 at 18:05
@HansPassant from my understanding, the underscore and '@4' in the second image indicates the calling convention is __stdcall. what would you suggest to solve my problem? — user11869, Oct 25 '13 at 18:11
@user11869 - But what is compiling them? C++ compiler or C compiler? — qxn, Oct 25 '13 at 18:24

score -1 · Answer 1 · edited May 23 '17 at 11:57

-1

It looks like the name _glIsQuery@4 was decorated (or mangled) by a C++ compiler. See this question (and particularly this answer that gives a pretty close example).

You may need an extern "C" if you want to use glIsQuery.

edited May 23 '17 at 11:57

Community

1
1

answered Oct 25 '13 at 18:14

qxn

17,162
3
49
72

failed to find entry point even though Dependency Walker says it's there

1 Answers1