Crash in Process.MainModule

Question

5.00/5 (1 vote)

See more:

Hi every one i have been using Process.MainModule.FileName to get the filename of all the running processes in a windowsXP32bit application. It was working fine. But the same 32-bit application crashed in 64-bit XP system giving the error as "Only part of a ReadProcessMemory or WriteProcessMemory request was completed"....Any suggestions?

one solution is building it with ANYCPU option...but my .exe is in C++ that loads the C# dll containing process related code. My C# dll is already set to ANYCPU configuration.But for my C++ .exe ANYCPU option will not be available.

Posted 11-Jul-10 18:25pm

Damy@chennai

Updated 11-Jul-10 19:49pm

Sandeep Mewara

v2

Add a Solution

Comments

E.F. Nijboer 12-Jul-10 6:32am

Shouldn't you be compiling for 64bit? instead of 32bit? So, even if AnyCPU isn't available, could you compile to 64-bit for 64-bit XP?

Rajasekharan Vengalil 12-Jul-10 17:44pm

Have you tried compiling your .NET DLL so that it targets x86 instead of "Anu CPU"? Since the process that loads your DLL is 32-bit, the DLL should also be 32-bit.

Sergey Alexandrovich Kryukov 10-Dec-10 11:35am

Interesting question, this one. Could you provide your C# code and give some information of the process (C++ borne, right?) which cause all the trouble? Do you have its C++ code? If so, could we see it.

In other words, what could be so special in this problematic process which makes it unique among all others not causing this problem (in principle, could be some super-puper mega-hack)?

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)