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/06/05 23:23:50 UTC
[Bug 2014] New: - "user breakpoint called" when deleting char strings created from transcode method off of DOMString
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2014
*** shadow/2014 Tue Jun 5 14:23:50 2001
--- shadow/2014.tmp.8945 Tue Jun 5 14:23:50 2001
***************
*** 0 ****
--- 1,37 ----
+ +============================================================================+
+ | "user breakpoint called" when deleting char strings created from transcode |
+ +----------------------------------------------------------------------------+
+ | Bug #: 2014 Product: Xerces-C |
+ | Status: NEW Version: 1.4 |
+ | Resolution: Platform: Other |
+ | Severity: Blocker OS/Version: Other |
+ | Priority: Other Component: DOM |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-c-dev@xml.apache.org |
+ | Reported By: kyle@paravoice.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ The problem I have been having is both strange and hard to reproduce in simple
+ examples.
+
+ When calling delete to clear memory created by DOMString.transcode, I will
+ receive a "User Breakpoint called from code at 'hex address'". This is called
+ from the NTDLL. This only happens in debug mode and not in every example of
+ this usage of transcode and deleting the char buffer it creates. The
+ application I am writing is very complex , but the the area that is in question
+ is rather simple. Just to repeat, the error does not occur in release
+ compiles. There is another issue which may be related. There is a large
+ memory leak in the release compile. With changes in the code, an example of
+ the transcode/delete very early in the program, developed the error. There was
+ no change in this part of the application, it was only moved from a dll into
+ the main program. At the same time the release version while not getting the
+ error, it does has a large memory leak. I am guessing that the delete function
+ while not generating an error, it is not clearing the memory.
+
+ I would appreciate any thoughts on this issue
+
+ Kyle Danielson
+ Paragon Voice Systems
\ 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