thanks for your help
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 01, 2001 3:48 PM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
"Christy, Rich" wrote:
> However, I do see several references to possib
"Christy, Rich" wrote:
> However, I do see several references to possible
> leaks in IDeepNodeListPool within calls to IDOM_NodeList
> getElementsByTagName(). Any ideas?
>
> Thanks
>
> Rich
I just looked into the code again, I think there is a small leak on the pool
instance. Anyway, I just ch
getElementsByTagName(). Any ideas?
Thanks
Rich
-Original Message-
From: Alberto Massari [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 10:29 AM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
At 08:08 AM 10/31/2001 -0800, you wrote:
>"Christy, Ric
At 08:08 AM 10/31/2001 -0800, you wrote:
>"Christy, Rich" wrote:
>
> > Actually purify was complaining of a memory leak with the list until I
> > deleted it.
>
>There may be an IDOM leak bug How does the caller retrieve parameter
>"const IDOM_Element *parentElement" ? If it is from the par
OK, I'll give that a try.
Thanks
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 10:09 AM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
"Christy, Rich" wrote:
> Actually purify was complaining of
"Christy, Rich" wrote:
> Actually purify was complaining of a memory leak with the list until I
> deleted it.
There may be an IDOM leak bug How does the caller retrieve parameter
"const IDOM_Element *parentElement" ? If it is from the parser, then memory
should be released when the parse
"Christy, Rich" wrote:
> What about what transcode returns. I thought any memory returned from that
> was the clients responsibility to delete.
>
Yes, so "delete[] transcodedElement" should be kept.
I only said that "delete list" not needed.
Tinny
-
.
Just a guess. It doesn't hold water if this is in fact the leak that Purify
was complaining about.
-Original Message-
From: Christy, Rich [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 10:22 AM
To: '[EMAIL PROTECTED]'
Subject: RE: delete[] problems with trans
]]
Sent: Wednesday, October 31, 2001 7:47 AM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
Rich,
I don't think it's related to transcode.
There's no need to "delete list", the IDOM implementation has its own memory
management. The only explicit delete
What about what transcode returns. I thought any memory returned from that
was the clients responsibility to delete.
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 7:47 AM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
/ need to delete list only (destructor does not delete elements in list)
>delete list;
>
>return element;
> }
>
> I core dumps on the call to transcode.
>
> Thanks,
>
> Rich
>
> -Original Message-
> From: Tinny Ng [mailto:[EMAIL PROTECTED]]
> Sent:
iginal Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 4:01 PM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
Christy,
Can you post more detail, e.g. how does IDOMStreamer::findElement call
transcode()?
Thanks!
Tinny
"Christy,
Christy,
Can you post more detail, e.g. how does IDOMStreamer::findElement call
transcode()?
Thanks!
Tinny
"Christy, Rich" wrote:
> After downloading and installing 1.5.2 official release, I started having
> core dumps calls to XMLString::transcode. The errors appear to be problems
> with new
13 matches
Mail list logo