[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Memory leak in svn_ra_local__get_file() for symlinks

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Sat, 23 Aug 2008 14:57:20 -0400

"Ph. Marek" <philipp.marek_at_bmlv.gv.at> writes:
> But I have to admit that here I can't reproduce the problem. This is a debian
> unstable i686, with 1.5.1; if the difference lies in the apr libraries or in
> the 64bit/32bit distinction I can't say ATM.

Dang. All I have is a Debian machine too (running 'testing' dist) :-(.
It doesn't reproduce for me either, using your script:

   (gdb) r
   Starting program: /usr/local/bin/svn cat file:///tmp/repos/bb
   [Thread debugging using libthread_db enabled]
   [New Thread 0xb79df6b0 (LWP 30977)]
   [Switching to Thread 0xb79df6b0 (LWP 30977)]
   
   Breakpoint 1, svn_ra_get_file (session=0x8eb5c40, path=0xb7f9a039 "",
       revision=1, stream=0x0, fetched_rev=0x0, \
       props=0xbfab9da8, pool=0x8eb5b98)
       at subversion/libsvn_ra/ra_loader.c:785
   785 SVN_ERR_ASSERT(*path != '/');
   (gdb)
   (gdb) shell cat /proc/`pidof svn`/status | grep Vm
   VmPeak: 7708 kB
   VmSize: 7708 kB
   VmLck: 0 kB
   VmHWM: 2444 kB
   VmRSS: 2444 kB
   VmData: 504 kB
   VmStk: 84 kB
   VmExe: 168 kB
   VmLib: 5444 kB
   VmPTE: 20 kB
   (gdb) n
   786 return session->vtable->get_file(session, path, revision, stream,
   (gdb) shell cat /proc/`pidof svn`/status | grep Vm
   VmPeak: 7708 kB
   VmSize: 7708 kB
   VmLck: 0 kB
   VmHWM: 2464 kB
   VmRSS: 2464 kB
   VmData: 504 kB
   VmStk: 84 kB
   VmExe: 168 kB
   VmLib: 5444 kB
   VmPTE: 20 kB
   (gdb) kill
   Kill the program being debugged? (y or n) y
   (gdb) q

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-23 20:57:38 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.