Uploaded image for project: 'Xerces-C++'
  1. Xerces-C++
  2. XERCESC-2091

DOMNormalizerTest behaves differently w/ VS2010 32-bit and 64-bit builds



    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 3.1.4
    • Fix Version/s: None
    • Component/s: DOM
    • Labels:
    • Environment:
      Visual Studio 2010 Version 10.0.40219.1 SP1Rel on Windows 7 Pro 64-bit OS w/ SP1, Intel i7-3740QM. Also reproduced with Xerces C++ 3.1.1 using same VS2010 version on Windows 10 Pro 64-bit OS, Intel i7-6700HQ.


      I used Subversion to pull down Xerces C++ v3.1.4. I then used Visual Studio to open ...\projects\Win32\VC10\xerces-all\xerces-all.sln. I set the active configuration to Debug x64 and did "Build"/"Rebuild solution" which succeeded. I then ran .../Build/Win64/VC10/Debug/DOMNormalizerTest.exe which caused an exception in like 198 of RefHashTableOf.c. The call stack started at line 290of Normalizer.cpp: doc->normalizeDocument();

      I then changed the active configuration to Debug Win32 and did "Build"/"Rebuild solution" which succeeded. I then ran .../Build/Win32/VC10/Debug/DOMNormalizerTest.exe which DID NOT cause an exception. The doc->normalizeDocument(); method returned and the document was successfully emitted:

      <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
      <po:docEle xmlns:po="http://www.test.com" xmlns:po2="http://www.test2.com">

      <docEleChildChild xmlns="http://www.test2.com"/>
      <docEleChildChild2 xmlns="http://www.test3.com"/>
      <po4:docEleChildChild3 xmlns:po4="http://www.test4.com"/>
      <po4:docEleChildChild4 xmlns:po4="http://www.test4.com"/>
      <docEleChildChild5 xmlns="http://www.test4.com"/>


      Which of these two behaviors is the expected (correct) behavior?
      What needs to be done to the build with the unexpected behavior in order to get the correct behavior?




            • Assignee:
              scantor Scott Cantor
              smartrun Alex Phillips
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: