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

Re: NULL-pointer access when merging with 1.5.1

From: Bernhard Merkle <bernhard.merkle_at_googlemail.com>
Date: Tue, 29 Jul 2008 07:33:53 +0200

On Mon, Jul 28, 2008 at 4:33 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:

> Hi,
>
> The following conditions will trigger a NULL-pointer access:
> * svn library 1.5.1 (I guess 1.5.0 too)
> * merge results in a conflict
> * user provides his own 'resolved' file in the conflict resolver callback
> * the users own 'resolved' file has a path *not* in the same folder than
> the conflicted file is located (best use a completely different path)
>

I thought SVN is also checked with Coverity (http://scan.coverity.com) ?

Coverity should find NULL pointers so I wonder if the current svn codebase
is not checked
or if Coverity does not find that specific case of NULL pointer.

thanks,
Bernhard.
Received on 2008-07-29 07:34:11 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.