How to handle access violation in strlen.asm while remote debugging ?

Question

1.00/5 (1 vote)

See more:

Firstly, I am very new to c++. Pardon my lack of knowledge.

This is a work project. We're running VS 2005 to develop in one machine and Remote Debugger to Debug the application(.exe) in another machine (both of of the machine do not have any internet connections). The application builds just fine but when debugged, it throws the error. Even if I put a breakpoint, the debugger doesn't go past the breakpoint no matter how many times I click continue. Now my problem is that I couldn't trace the error in a file that is written by Microsoft. Or maybe the error is not there and it is coming from another function that is using the file.

Here is an image of the problem.

Any small insight in this problem would help me do some more work on it.

Thanks.

What I have tried:

I've spent several days researching, and I came to know this kind of problem generally arises due to pointer pointing to null values or unsigned values.

Posted 19-Sep-19 5:18am

ribash1816

Updated 19-Sep-19 6:02am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2019-09-19T06:02:00

Solution 1

You will need to trap the exception in the debugger and look at the call stack, in order to find where in your code the error is generated. Always remember that just because the application build without errors does not mean it is error free.

Posted 19-Sep-19 6:02am

Richard MacCutchan

Comments

ribash1816 19-Sep-19 12:34pm

tracing the error through breakpoint, the function strlen is called in another file "atlsimpstr.h" :

static int __cdecl StringLength(__in_z_opt const char* psz) throw()
{
if(psz == NULL){
return( 0 );
}
return (int(strlen(psz)));
}

Richard MacCutchan 19-Sep-19 13:42pm

But that has nothing to do with your code. It is your code that causes the error so you need to go back to the actual place where it calls into these library functions.