managed heap corruption calling ADO .NET from native C++ exe

Question

0.00/5 (No votes)

See more:

More frequently in release than debug, I have a heap corruption error when I include a C++/CLR lib file. The error may be thrown before the first line in my executable executes.

C#

void _stdcall Execute_Query(const char * const Connection_String,
                            const char * const Query_Text,
                            bool const & Read_Only,
                            long & ErrorCode);

CLR can not be utilized with two separate libraries that I use in other projects, so I am isolating all CLR code in a separate dll.

The function Execute_Query above internally uses ADO .NET, but all of it's inputs are native C++. Is it incorrect to call the function above from Native C++ directly or do I need to use PInvoke or something else?

Posted 26-Sep-10 3:49am

T2102

Add a Solution

2 solutions

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)

E.F. Nijboer · Answer 1 · 2010-09-26T04:25:00

Solution 1

Native c++ is using the cdecl calling convention. Here an atricle about those calling conventions. This will already give some insight in the problem.
Calling Conventions Demystified[^]

Wrapper dll example:
Easy to use Wrapper (DLL) for Intel's OpenCV Library with Examples[^]

Good luck!

Posted 26-Sep-10 4:25am

E.F. Nijboer

Comments

T2102 27-Sep-10 1:21am

The Wrapper dll example is C# code. I am trying to find out if I need to do anything special to call function in a C++ dll that utilized ADO .NET, but whose function inputs are all native C++ types. I am able to call the function directly like I would any other native C++ dll function, however I want to know whether or not this could cause managed heap corruption.

T2102 27-Sep-10 1:22am

Note that I mainly work with native C++ and C++/CLI is incompatible with two other libraries I utilize, so I cannot use mixed programming. I also do not want to add the overhead of using C#.

T2102 · Answer 2 · 2010-09-27T02:11:00

Solution 2

This problem disappeared when I changed the compiler options to not use Whole Program Optimization.

Posted 27-Sep-10 2:11am

T2102