http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2769

*** shadow/2769 Tue Jul 24 10:08:15 2001
--- shadow/2769.tmp.20749       Tue Jul 24 10:08:16 2001
***************
*** 0 ****
--- 1,32 ----
+ +============================================================================+
+ | Purify detects "Invalid pointer read" during XMLPlatformUtils::Initialize( |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 2769                        Product: Xerces-C++              |
+ |       Status: NEW                         Version: 1.5.1                   |
+ |   Resolution:                            Platform: Sun                     |
+ |     Severity: Normal                   OS/Version: Solaris                 |
+ |     Priority: Other                     Component: Utilities               |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                  |
+ |  Reported By: [EMAIL PROTECTED]                                   |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Using gcc 2.95.2.
+ 
+ Simple test program containing only XMLPlatformUtils::Initialize() in main.
+ Purify reports "Invalid pointer read" - reading 4 bytes from 0xef6ca110 between 
+ the heap and the stack
+ 
+ Call stack is as follows :
+    main (foo.cpp:8)
+    XMLPlatformUtils::Initialize() (PlatformUtils.cpp:198)
+    XMLTransService::initTransService() (TransService.cpp:293)
+    ENameMapFor<XMLChTranscoder>::ENameMapFor<XMLChTranscoder>(const unsigned 
+ short *) (TransENameMap.hpp:104)
+ 
+ I notice that without purify the simple program doesn't crash.
+ This (IMHO) doesn't mean that the same memory violation isn't occurring 
+ though.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to