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 Robert Buck <rb...@mathworks.com> on 2002/06/20 15:37:15 UTC
Tinny, Alby: Follow up Question: Xerces-C .NET Project Files
Tinny:
I will manage the patches to the vc7 (visual studio .net) projects files as
you requested. I do have one question.
There is one change that I am making that I thought I should run by you, or
anyone else listening out there. Presently the xml4com project is deployed
to the "~\build\win32\xml4com" directory for vc6 projects. I would have
thought xml4com should have been put below the VC6 directory. Another
consequence of this is that it is deployed in a directory parallel to the
borland c++ directory. Really odd IMHO.
My suggestion is to put it down within the compiler specific directory. For
instance, going with the way I am suggesting the new directory layout would be:
build
win32
vc6
xml4com
... blah blah blah
vc7
xml4com
... blah blah blah
thoughts? Is this fine? Was there a particular reason this was never put
down one additional level, or perhaps is this just an artifact left over
from a prior rearrangement of the source/build tree?
Actually I just thought of a better question. Why is does the xml4com build
directory even exist? Shouldn't the build artifacts for the COM stuff also
go in the "build\win32\vc[6|7]\[debug|release]" directories? Is there a
reason for this?
Alberto, if you are listening into this conversation too, what are your
thoughts too?
Bob
At 03:49 PM 6/19/2002 -0400, you wrote:
>Bob,
>
>Yes, base upon the latest nightly source is appreciated.
>
>We hope to get VC.Net to our build machine soon, but not yet. Since we
>couldn't really verify your project files, please make sure they are tested,
>and if possible, willing to submit maintenance patch later.
>
>Thanks!
>
>Tinny
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Tinny: Xerces-C MS VS .NET Project Files Checked In
Posted by Robert Buck <rb...@mathworks.com>.
Tinny,
I have completed the upgrade to .NET. Please find the appropriate patches
and attached zip files at the bug database for the following items:
Bug #10065 : Updated COM Source File to eliminate error in .NET
Bug #10067 : Updated SEnumVal example source file to eliminate warning;
operator precedence mistake.
Bug #10180 : New Visual Studio .NET project files.
Question 1: Would it be possible to get these into source control for the
next nightly build?
------------------------------------------------
Let me detail what is still missing:
I need to modify packageBinaries.pl to autodetect VC6 vs VC7. I have it
mostly figured out. Just need to do more testing on that. I will follow up
on this one after the above is checked in. This means that it (presently)
only works with VC6, not VC7. Nothing new here yet.
Thanks
-Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
RE: memory leak in xerces c 2.0.0??
Posted by Dean Roddey <dr...@charmedquark.com>.
Unless I'm missing something, it's the usual thing where the tool is too
stupid to realize that its dealing with C++, and that the buffer
allocated in the constructor is later going to be freed in the
destructor. Don't trust those tools unless you look yourself and see
what's going on.
-------------------------------------
Dean Roddey
The Charmed Quark Controller
droddey@charmedquark.com
www.charmedquark.com
-----Original Message-----
From: eko@hns.com [mailto:eko@hns.com]
Sent: Thursday, July 25, 2002 2:14 PM
To: xerces-c-dev@xml.apache.org
Subject: memory leak in xerces c 2.0.0??
Hi,
I run the xerces c 2.0.0 under purify, and it show that it got memory
leak in
:
MLK: 612352 bytes leaked in 299 blocks
* This memory was allocated from:
malloc [rtlib.o]
c2n6Fi_Pv___1 [libCrun.so.1]
void*operator new(unsigned) [rtlib.o]
void*operator new[](unsigned) [rtlib.o]
XMLBuffer::XMLBuffer(int) [libxerces-c.so.20.0]
DOMDocumentTypeImpl::DOMDocumentTypeImpl(DOMDocument*,const
unsigned
short*,const unsigned short*,const unsigned short*,bool) [
DOMDocumentTypeImpl.cpp]
DOMDocumentType*DOMDocumentImpl::createDocumentType(const
unsigned
short*,const unsigned short*,const unsigned short*) [DOMDocu
mentImpl.cpp:299]
void AbstractDOMParser::doctypeDecl(const DTDElementDecl&,const
unsigned short*const,const unsigned short*const,const bool) [Ab
stractDOMParser.cpp:1007]
void XMLScanner::scanDocTypeDecl() [XMLScanner.cpp:2460]
void XMLScanner::scanProlog() [XMLScanner.cpp:2256]
void XMLScanner::scanDocument(const InputSource&)
[XMLScanner.cpp:446]
void AbstractDOMParser::parse(const InputSource&)
[AbstractDOMParser.cpp:339]
I run the same xml file using the same piece of code with a stable build
from
tar file
xerces-c-src_2002-07-14.tar, I don't see any memory leak related to the
parser
.
Do you think this is a real memory leak? If yes, Can it be fix soon??
Thanks !
Eva
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
memory leak in xerces c 2.0.0??
Posted by Eva Ko <ek...@hns.com>.
Hi,
I run the xerces c 2.0.0 under purify, and it show that it got memory leak in
:
MLK: 612352 bytes leaked in 299 blocks
* This memory was allocated from:
malloc [rtlib.o]
c2n6Fi_Pv___1 [libCrun.so.1]
void*operator new(unsigned) [rtlib.o]
void*operator new[](unsigned) [rtlib.o]
XMLBuffer::XMLBuffer(int) [libxerces-c.so.20.0]
DOMDocumentTypeImpl::DOMDocumentTypeImpl(DOMDocument*,const unsigned
short*,const unsigned short*,const unsigned short*,bool) [
DOMDocumentTypeImpl.cpp]
DOMDocumentType*DOMDocumentImpl::createDocumentType(const unsigned
short*,const unsigned short*,const unsigned short*) [DOMDocu
mentImpl.cpp:299]
void AbstractDOMParser::doctypeDecl(const DTDElementDecl&,const
unsigned short*const,const unsigned short*const,const bool) [Ab
stractDOMParser.cpp:1007]
void XMLScanner::scanDocTypeDecl() [XMLScanner.cpp:2460]
void XMLScanner::scanProlog() [XMLScanner.cpp:2256]
void XMLScanner::scanDocument(const InputSource&) [XMLScanner.cpp:446]
void AbstractDOMParser::parse(const InputSource&)
[AbstractDOMParser.cpp:339]
I run the same xml file using the same piece of code with a stable build from
tar file
xerces-c-src_2002-07-14.tar, I don't see any memory leak related to the parser
.
Do you think this is a real memory leak? If yes, Can it be fix soon??
Thanks !
Eva
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: Tinny: Xerces-C MS VS .NET Project Files Done
Posted by Tinny Ng <tn...@ca.ibm.com>.
Bob,
After you created the bug report, then query it. In the query page, there
is then a link to create attachement. Please try and let me know if does
not work Thanks!
Tinny
----- Original Message -----
From: "Robert Buck" <rb...@mathworks.com>
To: <xe...@xml.apache.org>
Sent: Friday, June 21, 2002 3:22 PM
Subject: Tinny: Xerces-C MS VS .NET Project Files Done
> Tinny,
>
> I have the VS .NET project files tested, cleaned up, etc. The doc on the
> bug database does not indicate how to submit files large files. Since
there
> are several here, and some are XML files, I'd prefer to submit them to
> someone as a zip file than upload them to the bug database. (there does
not
> seem to be an option for uploading files / attachments to a bug
> report). The project files unzipped come to about 300k. Zipped these are
> around 44k. A bit much to put into a text field of a bug submission form
> IMO. I'd like to have someone check these in so that these can get into
the
> soonest nightly build possible.
>
> What would you suggest?
>
> Bob
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Tinny: Xerces-C MS VS .NET Project Files Done
Posted by Robert Buck <rb...@mathworks.com>.
Tinny,
I have the VS .NET project files tested, cleaned up, etc. The doc on the
bug database does not indicate how to submit files large files. Since there
are several here, and some are XML files, I'd prefer to submit them to
someone as a zip file than upload them to the bug database. (there does not
seem to be an option for uploading files / attachments to a bug
report). The project files unzipped come to about 300k. Zipped these are
around 44k. A bit much to put into a text field of a bug submission form
IMO. I'd like to have someone check these in so that these can get into the
soonest nightly build possible.
What would you suggest?
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: Tinny, Alby: Follow up Question: Xerces-C .NET Project Files
Posted by Tinny Ng <tn...@ca.ibm.com>.
Bob,
I am not familiar with xml4com. And our team here does not maintain nor
test this component.
Actually if there is anyone out there who still uses the xml4com and knows
the stuff, we need volunteer to help the maintenance. There are a number
of outstanding bugzilla bugs regarding it, and our team does not have the
knowledge to fix them.
If nobody volunteer to patch this component, I would say don't even border
to include it in the new project files......
Tinny
----- Original Message -----
From: "Robert Buck" <rb...@mathworks.com>
To: <xe...@xml.apache.org>
Sent: Thursday, June 20, 2002 9:37 AM
Subject: Tinny, Alby: Follow up Question: Xerces-C .NET Project Files
> Tinny:
>
> I will manage the patches to the vc7 (visual studio .net) projects files
as
> you requested. I do have one question.
>
> There is one change that I am making that I thought I should run by you,
or
> anyone else listening out there. Presently the xml4com project is deployed
> to the "~\build\win32\xml4com" directory for vc6 projects. I would have
> thought xml4com should have been put below the VC6 directory. Another
> consequence of this is that it is deployed in a directory parallel to the
> borland c++ directory. Really odd IMHO.
>
> My suggestion is to put it down within the compiler specific directory.
For
> instance, going with the way I am suggesting the new directory layout
would be:
>
> build
> win32
> vc6
> xml4com
> ... blah blah blah
> vc7
> xml4com
> ... blah blah blah
>
> thoughts? Is this fine? Was there a particular reason this was never put
> down one additional level, or perhaps is this just an artifact left over
> from a prior rearrangement of the source/build tree?
>
> Actually I just thought of a better question. Why is does the xml4com
build
> directory even exist? Shouldn't the build artifacts for the COM stuff also
> go in the "build\win32\vc[6|7]\[debug|release]" directories? Is there a
> reason for this?
>
> Alberto, if you are listening into this conversation too, what are your
> thoughts too?
>
> Bob
>
>
> At 03:49 PM 6/19/2002 -0400, you wrote:
> >Bob,
> >
> >Yes, base upon the latest nightly source is appreciated.
> >
> >We hope to get VC.Net to our build machine soon, but not yet. Since we
> >couldn't really verify your project files, please make sure they are
tested,
> >and if possible, willing to submit maintenance patch later.
> >
> >Thanks!
> >
> >Tinny
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Tinny: Results of Porting to Xerces-C .NET Project Files
Posted by Robert Buck <rb...@mathworks.com>.
Tinny,
I got the project files working now for Visual Studio .NET. I am just
waiting for a response from Tinny on a prior email. Here are some results
that I have collated:
/#####################################
Build results:
1. various places:
d:\programs\vstudio\7.0\Vc7\include\useoldio.h(29) : warning
C4995: '_OLD_IOSTREAMS_ARE_DEPRECATED': name was marked as #pragma deprecated
**Resolution:
e.g. use <iostream> instead of <iostream.h> in visual
c++ 7.0 or newer; will defer implementation to later date.
no bug # assigned
2. xml4com:
statreg.cpp is obsolete. Please remove it from your project.
atlimpl.cpp is obsolete. Please remove it from your project.
3. xml4com.def
..\..\..\..\..\src\xercesc\com\xml4com.def : warning LNK4222:
exported symbol 'DllCanUnloadNow' should not be assigned an ordinal
..\..\..\..\..\src\xercesc\com\xml4com.def : warning LNK4222:
exported symbol 'DllGetClassObject' should not be assigned an ordinal
..\..\..\..\..\src\xercesc\com\xml4com.def : warning LNK4222:
exported symbol 'DllRegisterServer' should not be assigned an ordinal
..\..\..\..\..\src\xercesc\com\xml4com.def : warning LNK4222:
exported symbol 'DllUnregisterServer' should not be assigned an ordinal
**Items 2 & 3 are bug # 10065 See bug report for details of appropriate
fixes. Someone will need to review the suggested changes and check the
changes in for me. It would be ideal to have these commited to source
control for the next release.
##################################
SEnumVal:
SEnumVal.cpp:
d:\development\3rd-party\xerces\latest\xerces-c-src_2002-06-18\samples\SEnumVal\SEnumVal.cpp(316)
: warning C4554: '&' : check operator precedence for possible error; use
parentheses to clarify precedence
d:\development\3rd-party\xerces\latest\xerces-c-src_2002-06-18\samples\SEnumVal\SEnumVal.cpp(319)
: warning C4554: '&' : check operator precedence for possible error; use
parentheses to clarify precedence
d:\development\3rd-party\xerces\latest\xerces-c-src_2002-06-18\samples\SEnumVal\SEnumVal.cpp(322)
: warning C4554: '&' : check operator precedence for possible error; use
parentheses to clarify precedence
Microsoft's warning is valid. For example:
( mflags & SchemaSymbols::NILLABLE != 0 )
is poorly written and will be evaluated improperly since "!=" has higher
precedence than "&".
** Bug # 10067 details the problem and corrective action. It would be ideal
to have these commited to source control for the next release.
######################################
Test results:
Ran the test script in "scripts" and all looks fine there.
--Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: Tinny, Alby: Follow up Question: Xerces-C .NET Project
Files
Posted by Alberto Massari <al...@exln.com>.
Hi Bob,
At 06.37 20/06/2002 -0700, Robert Buck wrote:
>[...]
>Actually I just thought of a better question. Why is does the xml4com
>build directory even exist? Shouldn't the build artifacts for the COM
>stuff also go in the "build\win32\vc[6|7]\[debug|release]" directories? Is
>there a reason for this?
>
>Alberto, if you are listening into this conversation too, what are your
>thoughts too?
IMO, the output of xml4com should go in the same [debug|release] directory
used by the same compiler (I guess xml4com needs to dynamically load the
Xerces DLL, and it's easier to have it in the same directory instead of
changing the PATH env variable).
But I never used nor compiled xml4com, so my opinion is not really an
informed one...
Alberto
-------------------------------
Alberto Massari
eXcelon Corp.
http://www.StylusStudio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org