You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2001/08/08 23:37:55 UTC
[Bug 3052] New: - IDOM problem with multiple parses
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3052
*** shadow/3052 Wed Aug 8 14:37:55 2001
--- shadow/3052.tmp.9438 Wed Aug 8 14:37:55 2001
***************
*** 0 ****
--- 1,32 ----
+ +============================================================================+
+ | IDOM problem with multiple parses |
+ +----------------------------------------------------------------------------+
+ | Bug #: 3052 Product: Xerces-C++ |
+ | Status: NEW Version: 1.5.1 |
+ | Resolution: Platform: HP |
+ | Severity: Critical OS/Version: HP-UX |
+ | Priority: Other Component: DOM |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-c-dev@xml.apache.org |
+ | Reported By: seg@icon.co.za |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ The previous bugs relating to IDOM segfaults when using getElementsByTagName
+ refers. The getLength() problem is now fixed (in the 08-08-2001 source). The
+ next problems experienced are as follows:
+
+ (a) Using getElementsByTagName on a IDOM_Document * results in a core dump on
+ HP-UX. Any reason why in DOM a document could be used to obtain elements by tag
+ name but not in IDOM?
+
+ (b) I use a test utility to test 1000 parse cycles in a multi-threaded
+ environment using IDOM. While I exclude getElementsByTagName and getLength on
+ the resulting IDOM_NodeList *, I achieve extremely good results and stability.
+ However, the moment I include getElementsByTagName, the first parse and access
+ to the IDOM_NodeList succeeds. In the second parse however, a core dump results
+ and it can be traced to the IDDeepNodeListPool.cpp file. I have recursively
+ traversed the DOM structure after a parse and all elements are present in the
+ document. I am working on the 08-08-2001 source code in which bug 2979 is fixed.
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org