DO NOT REPLY [Bug 27052] - SchemaAttDef::serialize() leaks memory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27052] - SchemaAttDef::serialize() leaks memory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Placement operator delete invocation is not yet implemented.

Hi David, Thanks for several pointers, dealing with it one by one to make it work. Sorry, I did not mean to say I had problem building/linking Xerces library instead I have problem when I run my servers with path pointing to Xerces 2.5 library than the earlier 2.2. I have a binary version and d

Re: Re: unresolved symbols (external)

Alberto, Object/library modules... ..\..\common\xerces-lib\xerces-c_2D.lib zlib.lib pp5c.lib pp5e.lib ppxl.lib pscript.lib advapi32.lib user32.lib kernel32.lib winspool.lib gdi32.lib umpdddi.lib ntdll.lib msvcrt.lib additional... $(DDK2K)\libchk\i386,..\Lib\Debug,..\Lib\zlib\Debug,..\PDL\PP5C\

Re: Re: unresolved symbols (external)

At 09.52 03/03/2004 -0800, Jimmy Yu wrote: Dear Alberto, The information were all already in the link tab, further, the real interesting thing is that only the XMemory.cpp file and XString.cpp file's function calls were unresolved. I have included the 2 function calls that is in my program... No,

RE: Not able to make XercesDOMParser Schema Validation working

Just to close the case: I wasnt having an error handler of my own and accordingly didnt get any exceptions thrown in my method, even that I had try-catch arround the {pParser->parse(XMLFileName)}. Now after having implementd the class MyErrorHandler : public ErrorHandler and doing: pParser->setE

Re: Re: unresolved symbols (external)

At 09.34 03/03/2004 -0800, Jimmy Yu wrote: Dear Alberto, In the setting for the whole project, I chose 'Engine' and under the link tab, I have put in the correct path to where the debug and release of xerces-c_2D.lib and xerces-c_2.lib and the corresponding dll files are in the same directory. (Is

RE: Placement operator delete invocation is not yet implemented.

Hi, The mangled names suggest you have old objects or old header files in the build, since the missing symbols are in the namespace "xercesc_2_2". >From what I can see, this doesn't have anything to do with building the Xerces-C library, although your email seemed to suggest the missing symbo

Re: unresolved symbols (external)

At 09.08 03/03/2004 -0800, Jimmy Yu wrote: Hello, My previous 2 postings didn't get through (At least they weren't on the web site.) If this is a repeat for you, please forgive me. I am using VC++ 6.0, before I merged my code into the main project, everything was fine independently. However, now I

unresolved symbols (external)

Hello, My previous 2 postings didn't get through (At least they weren't on the web site.) If this is a repeat for you, please forgive me. I am using VC++ 6.0, before I merged my code into the main project, everything was fine independently. However, now I am getting these errors below. If anyone

RE: Placement operator delete invocation is not yet implemented.

Hi Dave, That's very strange. My fault.. please see the sample of unresolved symbols that I get during startup of my executables below...it's actually the same as the warnings during build. As I said earlier these symbols exist in 2.2 version but in 2.5. *** /usr/lib/dld.sl: U

More release() questions...

Title: More release() questions... Hi All, I am just getting back to the xerces-c-dev mailing list after a long time.  I did browse the archives before posting, so sorry if I may have missed any response on this. From what I understand, just releasing element nodes does not free up the mem

RE: Placement operator delete invocation is not yet implemented.

Hi, Have you tried with Xerces-C 2.4 source? If that works, then you could hack the 2.5 source for XMemory.cpp and XMemory.hpp in the same way the 2.4 versions were hacked, and this *should* keep the compiler happy. Or, you could try and upgrade your compiler... Cheers, Neil Neil Graham XM

RE: Placement operator delete invocation is not yet implemented.

Hi, This warning does not cause any unresolved symbol problems on HP. I get the same warnings when I build, but have no problems linking and running with Xerces-C 2.5. If you posted a _small_ snippet of some of the unresolved symbols, someone might be able to help, but you've not done that y

RE: Placement operator delete invocation is not yet implemented.

Hello Neil, Appreciate your feedback. We are using aCC version A.03.25. From what you say, it's in the middle. What do you suggest? Can you point to a stable version of xerces earlier than 2.5 that can handle this. It would be nice to have the latest i.e 2.5 and if so is there a way to work

RE: Placement operator delete invocation is not yet implemented.

Hello Dave, We do see it as warnings because I did not do a forced build using -u option of clearmake and let the winking work. That meant it still was referring to xerces 2.2 version. Anyway, when I deployed my executables that's when I saw the unresolved symbols. Please note that in the depl

DO NOT REPLY [Bug 7051] - "hash" argument clashes with STL's hash

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 3347] - Memory deallocation

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug