MFC executable gets exit without any error while debugging with visual studio 2012

Question

1.44/5 (2 votes)

See more:

, +

I am currently developing some addition code as dll for one third party executable. For debug of my DLL using third party exe, I am providing executable path in debugging property.
Project property

All things are working properly unless they release new version of executable. They released new version of executable may be with updated Visual studio version or .NET framework or new thread with new component. With new executable when I run exe from my DLL solution, exe gets stop with following information:

C++

The thread 0x2778 has exited with code 255 (0xff).
The thread 0x1330 has exited with code 255 (0xff).
The thread 0x207c has exited with code 255 (0xff).
The thread 0x10e8 has exited with code 255 (0xff).
The thread 0x874 has exited with code 255 (0xff).
The thread 0x2788 has exited with code 255 (0xff).
The thread 0xef4 has exited with code 255 (0xff).
The thread 0x2548 has exited with code 255 (0xff).
The program '[8004] abc.exe' has exited with code 255 (0xff).

My last 2 hours of google give me following links but not fruitful to give a solution.

Kindly provide more information about why exe gets stop?

What I have tried:

program.exe: Native' has exited with code 255 (0xff)[^]

Native' has exited with code 3 (0x3)[^]

Posted 12-Sep-16 4:21am

Coder Block

Updated 12-Sep-16 23:30pm

Add a Solution

Comments

[no name] 12-Sep-16 10:26am

Magic 8 Ball says, "Cannot predict now"

Richard MacCutchan 12-Sep-16 10:58am

I would guess there is a bug in someone's code. However, since we have no idea what any of the code is trying to do, that's the best guess. You need to do some debugging to isolate where the error is occurring.

Richard MacCutchan 13-Sep-16 5:38am

Updating your question without providing more information is not going to help. As I said yesterday, we have no idea what your program or libraries are doing so it is impossible to make any suggestion other than getting together with your third party and doing some debug testing.

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)

KarstenK · Answer 1 · 2016-09-12T07:19:00

Solution 1

Using some dlls with an exe should be from the same version of Visual Studio. So use the same VS as the dlls are build on.

One minute of Google led my to such error 255 cause. It also can be some linking mismatch (static/dynamic). Maybe the other party changed it.

Send them your files and asked for comments..

Posted 12-Sep-16 7:19am

KarstenK

Comments

CPallini 13-Sep-16 5:54am

5.