Dll loaded into an application space which is built with /LARGEADDRESSAWARE flag

Question

0.00/5 (No votes)

See more:

Hi,
I have an application that is built with the /LARGEADDRESSAWARE linker flag. I have a dll from a third party that is loaded into this application space.I am unaware of its build settings. Will the benefit of accessing memory greater than 2GB, be available for this dll functions too?

What I have tried:

I am getting a crash when i am calling a dll function to write something to the file. The application stores a lot of data in its buffer internally. So i doubt that this could be because of not handling exception thrown by new(may be).

Posted 21-Mar-17 7:43am

kuttiylajai

Updated 22-Mar-17 4:30am

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)

Jochen Arndt · Accepted Answer · 2017-03-22T04:30:00

Solution 1

The setting applies to the process and therefore also to DLLs loaded by the process.

But the functions within the DLL might not be able to handle addresses beyond 2 GB. You have to ask the supplier of the DLL.

Posted 22-Mar-17 4:30am

Jochen Arndt