Access Violation with xlfCaller

Question

0.00/5 (No votes)

See more:

I am getting an access violation when I try to get the Excel caller when I evaluate a defined name that equals a UDF of another defined name.

In particular, I am getting an access violation when I try to find the Caller.

Is there a way I can tell whether the access violation is from Excel itself or from my code?

The following code crashes

C++

Excel4(xlfCaller, x, 0)

When it's reached anywhere else, it has never crashed.
When I comment out this code, no crash occurs...

Posted 16-Jun-11 11:27am

T2102

Updated 16-Jun-11 12:11pm

v2

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)

OlegKrivtsov · Accepted Answer · 2011-06-16T23:49:00

Solution 1

You can attach to the Excel.exe process with the help of Visual Studio. In your Visual Studio window, open menu Debug->Attach to process.. and select Excel.exe in the list. Then do what you typically do. When excel crashes, Visual Studio will show you the Call Stack window and you will be able to see the exact place of the code.

Posted 16-Jun-11 23:49pm

OlegKrivtsov

Comments

T2102 17-Jun-11 8:19am

Thanks, I spent several hours reviewing and I'm 99% sure this is a memory error in Excel's API and not my code.