Integrate:

Integrate:
[ 27801]
Subject: [PATCH] doop.c: (Coverity) found a bug but not quite what Coverity thought it did (try valgrind on the new bop.t without the doop.c patch)
Date: Thu, 13 Apr 2006 19:20:46 +0300 (EEST)
Message-Id: <20060413162046.5F9636D08C@ugli.hut.fi>

[ 27856]
The danger of piping an mbox to patch is that it contains more than
one message. So both:

Subject: [PATCH] doop.c: one more code path where memory could leak (Coverity)
From: jhi@cc.hut.fi (Jarkko Hietaniemi)
Message-Id: <20060416081925.680336CF2D@aprikoosi.hut.fi>
Date: Sun, 16 Apr 2006 11:19:25 +0300 (EEST)

and

Subject: [PATCH] doop.c: one more code path where memory could leak (Coverity)
From: jhi@cc.hut.fi (Jarkko Hietaniemi)
Message-Id: <20060416081925.680336CF2D@aprikoosi.hut.fi>
Date: Sun, 16 Apr 2006 11:19:25 +0300 (EEST)

[ 27857]
Revert 27856.

[ 27859]
Subject: [PATCH] dooop.c: the strong asserts in Sv* macros could cause memory leakage -- move the macro calls earlier (Coverity CID 84)
From: jhi@cc.hut.fi (Jarkko Hietaniemi)
Message-Id: <20060417071937.C13346CF2D@aprikoosi.hut.fi>
Date: Mon, 17 Apr 2006 10:19:37 +0300 (EEST)

[ 27883]
Coverity still thinks that there is a route through do_vop that can
leak resources. I believe that it's spotted that you can skip all the
cases in the switch. Plug that hole.
p4raw-link: @27883 on //depot/perl: 4154741246a440c7ccc4e633e6d115949af4ee56
p4raw-link: @27859 on //depot/perl: 9fdd7463b7e8360d31fec7e9c836e5883fb01a87
p4raw-link: @27857 on //depot/perl: 3ce4c5325c6bf80779666a9007ef3a4d29f4fce1
p4raw-link: @27856 on //depot/perl: 2d78db9da3a2e0242b1652394b939dc5b5fab5e5
p4raw-link: @27801 on //depot/perl: 794a0d33eec8a6056eaa14b2e6eae594c8004a65

p4raw-id: //depot/maint-5.8/perl@29950
p4raw-integrated: from //depot/perl@27859 'edit in' doop.c (@27857..)
p4raw-integrated: from //depot/perl@27801 'merge in' t/op/bop.t
	(@26136..) pod/perlapi.pod (@27626..) sv.c (@27794..)