You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by an...@locus.apache.org on 2000/10/20 03:20:46 UTC
cvs commit: xml-xerces/c/doc faq-parse.xml readme.xml
andyh 00/10/19 18:20:45
Modified: c/doc faq-parse.xml readme.xml
Log:
Add a couple of FAQ entries
Revision Changes Path
1.18 +43 -0 xml-xerces/c/doc/faq-parse.xml
Index: faq-parse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-parse.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- faq-parse.xml 2000/10/12 18:47:37 1.17
+++ faq-parse.xml 2000/10/20 01:20:44 1.18
@@ -162,6 +162,49 @@
</faq>
+
+<faq title="Can't debug into the xerces DLL with the MSVC debugger">
+ <q>
+ The libs/dll's I downloaded keep me from using the debugger in VC6.0 . I
+ am using the 'D', debug versions of them. "no symbolic information
+ found" is what it says. Do I have to compile everything from source to
+ make it work?
+ </q>
+ <a><p>Unless you have the .pdb files, all you are getting with the debug library
+ is that it uses the debug heap manager, so that you can compile your stuff
+ in debug mode and not be dangerous. If you want full symbolic info
+ for the xerces library, you'll need the .pdb files,
+ and to get those, you'll need to rebuild the xerces library.</p>
+ </a>
+ </faq>
+
+<faq title="First-chance exception in Microsoft debugger">
+ <q>"First-chance exception in DOMPrint.exe (KERNEL32.DLL):
+ 0xE06D7363: Microsoft C++ Exception." I am always getting
+ this message when I am using the parser. My programs are
+ terminating abnormally. Even the samples are giving this
+ exception. I am using Visual C++ 6.0 with latest service
+ pack installed.</q>
+
+ <a>
+ <p>XML4C uses C++ exceptions internally, as part of its normal operation. By
+ default, the MSVC debugger will stop on each of these with the "First-chance
+ exception ..." message.
+ </p>
+ <p>To stop this from happening do this:</p>
+ <ul>
+ <li>start debugging (so the debug menu appears)</li>
+ <li>from the debug menu select "Exceptions"</li>
+ <li>from the box that opens select "Microsoft C++ Exception"
+ and set it to "Stop if not handled" instead of "stop always".</li>
+ </ul>
+
+ <p>You'll still land in the debugger if your program
+ is terminating abnormally, but it'll be at your problem, not from
+ the internal XML4C exceptions.</p>
+ </a>
+</faq>
+
<faq title="I am seeing memory leaks for Xerces-C. Are they real?">
<q>I am seeing memory leaks for Xerces-C. Are they real?</q>
<a>
1.9 +2 -2 xml-xerces/c/doc/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/readme.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- readme.xml 2000/09/25 02:03:02 1.8
+++ readme.xml 2000/10/20 01:20:45 1.9
@@ -15,8 +15,8 @@
<jump href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core.html">DOM 1.0</jump>,
<jump href="http://www.megginson.com/SAX/SAX1/index.html">SAX 1.0</jump>,
<jump href="http://www.megginson.com/SAX/index.html">SAX 2.0</jump>,
- <jump href="http://www.w3.org/TR/REC-xml-names/">Namespaces</jump>),
- <jump href="http://www.w3.org/TR/1999/CR-DOM-Level-2-19991210/">DOM Level 2 version 1.0</jump>.
+ <jump href="http://www.w3.org/TR/REC-xml-names/">Namespaces</jump>,
+ <jump href="http://www.w3.org/TR/1999/CR-DOM-Level-2-19991210/">DOM Level 2</jump>).
The parser provides high performance, modularity, and scalability.
Source code, samples and API documentation are provided with the parser. For
portability, care has been taken to make minimal use of templates,