Binaries are crashing which are compiled with VS2013 platform tool set visual studio 2013 - windows XP (v120_xp)

Question

0.00/5 (No votes)

See more:

VS2013

Hi Friends

I have list of binaries which are compiled with Visual Studio 2010 and working fine with Windows Server 2003

but when I compiled with Visual Studion 2013 with platform tool set -> Visual Studio 2013 - Windows XP (v120_xp) and binaries are getting crashing at Windows Server 2003.

It is not happening on all Windows Server 2003 but on few servers .

When I created memory dump with debug build, it point out some line in source code where binaries are getting crash is nothing a simple arithmetic calculation like

int a = c+d ;

As per observation from binaries log file, binaries started execution successfully and crashed mid of the execution .

Please guide me what could I do to fix this issue ?

What I have tried:

1. analysed with windb
2. analysed with application verifier tool

Posted 2-Jun-16 4:47am

paul crescent

Updated 2-Jun-16 4:57am

Add a Solution

Comments

Sergey Alexandrovich Kryukov 2-Jun-16 11:45am

Hard to say, based on this information.
At this moment, my only doubt is: does the target CPU match the actual CPU on the system where you have crash?
Is one of the platforms IE-64? Is your target platform of the application x86, or something else?
—SA

barneyman 2-Jun-16 18:15pm

you're guessing until you debug it - windbg or vs remote debugging - the latter is easier, the former less invasive

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-06-02T04:57:00

Solution 1

I think that is incompatibility of the VS 2013 to XP. Try to lower some compiler settings like the _WINVER_ macro.

Read the Visual Studio 2013 Compatibility and focus on the fine-printed additions.

Solution: use an older version like VS 2010 to target Windows XP.

Posted 2-Jun-16 4:57am

KarstenK