We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
10 days, 3 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Memory cannot be referenced error
Posted on 2001-08-15
Hi,
I have this C++ codes that I cut and paste from a working program, but to my dismay gives me the following run time error:
The instruction at "0x0012f9de" referenced memory at "0x0000000000". The memory could not be "read".
Click on OK to terminate program
Click on Cancel to debug
Pls help.
-------------------
// Source code is as follows:
typedef WORD (*OPEN)(WORD, BYTE*, WORD*)
....
OPEN my_open
BYTE msg[256];
WORD rlen;
WORD rcode;
hDLL = LoadLibrary(_T("myopen.dll
if (hDLL!=NULL)
{
my_open = (OPEN)GetProcAddress(hDLL,
if (my_open!=NULL)
{
// Run time error traced to below call
rcode = (my_open)(0, msg, &rlen);
}
}
----------
I have this C++ codes that I cut and paste from a working program, but to my dismay gives me the following run time error:
The instruction at "0x0012f9de" referenced memory at "0x0000000000". The memory could not be "read".
Click on OK to terminate program
Click on Cancel to debug
Pls help.
-------------------
// Source code is as follows:
typedef WORD (*OPEN)(WORD, BYTE*, WORD*)
....
OPEN my_open
BYTE msg[256];
WORD rlen;
WORD rcode;
hDLL = LoadLibrary(_T("myopen.dll
if (hDLL!=NULL)
{
my_open = (OPEN)GetProcAddress(hDLL,
if (my_open!=NULL)
{
// Run time error traced to below call
rcode = (my_open)(0, msg, &rlen);
}
}
----------
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
-
2
- +2
8 Comments
May be problem in name of function from dll. For know exectly all name of functions I use TDump utility of Borland.
> May be problem in name of function from dll. For know exectly all name of functions I use TDump utility
of Borland.
I don't think this is the problem, because the GetProcAddress() would return NULL in this case...
I suspect the problem coud be in the variable msg. You are reserving 256 bytes of the memory for it. Are you sure that your DLL function is accessing only that range of memory?
Do you have access to the myopen.dll code?
of Borland.
I don't think this is the problem, because the GetProcAddress() would return NULL in this case...
I suspect the problem coud be in the variable msg. You are reserving 256 bytes of the memory for it. Are you sure that your DLL function is accessing only that range of memory?
Do you have access to the myopen.dll code?
Nothing wrong with the parameters, strange thing is it can work in debug version but crashes in release version, any idea?
O, it is difference between Debug and Release version in VC. There are many Q in EE about this issue, but I work in BC and can't help you. Sorry.
The problem could be in the implementation of the function
in the DLL. One of the differences between Realese and
Debug, is that Debug version gives you some protection, such as "preparing" the stack with padding characters.
It could be that the function you call, is has a fault
which causes it not to run properly in a Release version.
in the DLL. One of the differences between Realese and
Debug, is that Debug version gives you some protection, such as "preparing" the stack with padding characters.
It could be that the function you call, is has a fault
which causes it not to run properly in a Release version.
I've just read the Etiquette page, and I wanted to
apologize on sending an Answer, instead of a Comment.
Udil
apologize on sending an Answer, instead of a Comment.
Udil
oohchild,
Do you still need help with this?
The answer is almost certainly that you have reversed the correct order of parameters.
Perhaps there is an old version of myopen.dll that used different parameter type or sequence. If that copy of myopen.dll is in the Release directory, it would be called. While the good one (in your Debug directory) would be working fine for debug builds.
-- Dan
Do you still need help with this?
The answer is almost certainly that you have reversed the correct order of parameters.
Perhaps there is an old version of myopen.dll that used different parameter type or sequence. If that copy of myopen.dll is in the Release directory, it would be called. While the good one (in your Debug directory) would be working fine for debug builds.
-- Dan
Featured Post
Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Unlike C#, C++ doesn't have native support for sealing classes (so they cannot be sub-classed). At the cost of a virtual base class pointer it is possible to implement a pseudo sealing mechanism
The trick is to virtually inherit from a base class…
Written by John Humphreys
C++ Threading and the POSIX Library
This article will cover the basic information that you need to know in order to make use of the POSIX threading library available for C and C++ on UNIX and most Linux systems.
[s…
The goal of the video will be to teach the user the concept of local variables and scope. An example of a locally defined variable will be given as well as an explanation of what scope is in C++. The local variable and concept of scope will be relat…
The viewer will learn additional member functions of the vector class. Specifically, the capacity and swap member functions will be introduced.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month10 days, 3 hours left to enroll
623 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.