On Fri, May 02, 2003 at 10:07:14PM -0500, John Goerzen wrote:
> Olaf Hering <olh@suse.de> writes:
>
> > I get this since a while. Is this still supposed to work with the
> > latest svn? I'm not sure what version is used on the remote side, but I
> > guess its 0.21.*:
>
> I've been seeing the same with svn log, and like you, using svnserve.
> For me, it happens more when the data to be returned by svn log is
> large. Does that agree with your experiences with svn diff?
>
> I reported it earlier today as issue #1281 at
> http://subversion.tigris.org/issues/show_bug.cgi?id=1281.
>
> -- John
>
I can reproduce this problem in a few easy steps:
svnadmin create f
svn mkdir -m "message" file://$PWD/f
perl -e 'print "A"x4502355' > big-message
svn ps --revprop svn:log -r 1 -F big-message file://$PWD/f
svnserve -X #or gdb it
svn log -r 1 svn://localhost$PWD/
I believe it to be a pools/vformatter bug. It appears (to me) to be the
same one that was reported as a potential buffer-overflow a few months
ago.
It is proving to be very difficult to track down; I will try building
APR without -O2 to see if that makes the debugging easier.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 6 17:03:11 2003