On Wed, 2005-08-03 at 11:02 -0400, David James wrote:
> On 8/2/05, Christopher Ness <chris@nesser.org> wrote:
> > Ok, here is my configure info and some version info:
> Chris, thanks a lot for sending me this information! It is very helpful!
>
> I've committed fixes in r15565 and r15566. More details below.
No problem.
I updated to r15566 and recompiled/tested.
Things ran just fine. The tests passed.
<snip>
> > /home/nesscg/sandbox/python-bindings-improvements/subversion/include/svn_types.h:431: Warning(451): Setting const char * member may leak memory.
> > /home/nesscg/sandbox/python-bindings-improvements/subversion/include/svn_types.h:432: Warning(451): Setting const char * member may leak memory.
> > /home/nesscg/sandbox/python-bindings-improvements/subversion/include/svn_types.h:433: Warning(451): Setting const char * member may leak memory.
> > /home/nesscg/sandbox/python-bindings-improvements/subversion/include/svn_types.h:434: Warning(451): Setting const char * member may leak memory.
> > /home/nesscg/sandbox/python-bindings-improvements/subversion/include/svn_string.h:85: Warning(451): Setting const char * member may leak memory.
>
> These warnings signal potential memory leaks, because SWIG and Python
> don't keep track of the memory during Python->C variable assignments.
> This bug is present on trunk as well. We haven't come up with a good
> solution to this yet. Ideas?
I don't know as my experience with python is minimal and SWIG is
non-existent. But if SWIG and Python don't keep track of the memory,
than there is only one thing left to do it, right?
Cheers,
Chris
--
Wireless Group
McMaster University
summer
11:38:26 up 12 days, 21:31, 1 user, load average: 0.04, 0.05, 0.07
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 3 17:47:07 2005