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=3369

*** shadow/3369 Tue Sep  4 18:59:53 2001
--- shadow/3369.tmp.649 Tue Sep  4 21:26:33 2001
***************
*** 140,143 ****
  Even though it may not be "as simple as the Init and Term methods", would you 
  care to humor me just a bit more by removing all calls to 
  XMLPlatformUtils::Terminate() entirely from the application, and then seeing 
! what happens?
--- 140,165 ----
  Even though it may not be "as simple as the Init and Term methods", would you 
  care to humor me just a bit more by removing all calls to 
  XMLPlatformUtils::Terminate() entirely from the application, and then seeing 
! what happens?
! 
! ------- Additional Comments From [EMAIL PROTECTED]  2001-09-04 21:26 -------
! Hello Eric,
! 
!      I removed the call to Terminate as you wished, but I am still getting
! access violations from the lib.  I have watched my break points on Init and
! Term.  They will only ever be called the first time I run the dll(application)
! after any given load.  The pattern still follows work, crash, work, crash, but
! the pattern does this because the dll is killing out and having to be reloaded.
!  At least this is the theory I've come to.  
! 
!      This may possibly be a Borland and MS issue.  I've come to my conclusion of
! the work crash work crash based on the fact that during a debug session I can
! only run one time successfully without having to reset the program.  The erratic
! state is being caused in calls behind the scenes in the parse method, or in code
! not visible to my debugger(C++ code that is).  When I get time I will build the
! lib into my project so I can debug all the way through. 
! 
!      Have there been more issues with Borland builds than any other?  I am
! curious.  
! 
! Thanks for your help.  Wade.

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

Reply via email to