Is there a possibility that an error comming on 64bit build will not come on 32bit build?

Question

0.00/5 (No votes)

See more:

Hi,
Is there a possibility that an error comming on 64bit build will not replicate on 32bit build(and visa virsa) on Visual studio 2010 with unmanaged C++.

Posted 8-Aug-12 21:41pm

ahsanriaz1K

Updated 8-Aug-12 21:43pm

v2

Add a Solution

Comments

barneyman 9-Aug-12 3:45am

completely possible, if you're walking past the bounds of an allocated pointer, for instance

Richard MacCutchan 9-Aug-12 3:49am

What does it matter? The important thing is that you find the error and fix it.

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)

Eugen Podsypalnikov · Accepted Answer · 2012-08-08T22:02:00

Yes :) , the following code will generate
an "dividing by zero" exception faster for 32bit build:

C++

{
  UINT_PTR uiDivider(0);
  for (;;) {
    UINT_PTR uiResult(4 / ++uiDivider);
  }
}

...and this can crash an 64bit execution:

C++

{
  class A {
    int m_iMember;
  public:
    A(int i = 0) : m_iMember(i) {}
    int GetMmber() const { return m_iMember; }
  } a;

  A* pA(&a);
  DWORD dwPointerStorage = static_cast<dword>(pA);
  pA = static_cast<a*>(dwPointerStorage);
  pA->GetMember(); // possible crash for 64bit :)
}</dword>

pasztorpisti · Accepted Answer · 2012-08-08T22:44:00

Unfortunately there are a lot of spots for programmers to make architecture specific bugs. For example relying on the size of a C++ type, different compiler settings for Win32 and x64 (like alignment) and so on...
On the other hand be careful when debugging because:
- Your uninitialized variables are filled up with marker data in debug builds.
- Often your uninitialized variables are filled up with zeros in release builds when you run them from the debugger from your ide.
- Your uninitialized variables are left as they are if you start the executable manually and then you attach to the process later with your debugger. Unfortunately some bugs can be caught only with this technique that is the most circumstantial.

Is there a possibility that an error comming on 64bit build will not come on 32bit build?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0