hugin-devs team mailing list archive

[rew <721136@xxxxxxxxxxxxxxxxxx>]

On Sun, Dec 01, 2013 at 07:31:06PM -0000, Lukas Wirz wrote:
> If I recompile without openmp I get exactly the same output.
> Image_cache has been disabled in 842, so I can't switch that on.  I'll
> spend some time having fun with valgrind.

Good idea. Valgrind will be able to find problems when you "overstep"
a boundary of a pointer. The effects we're seeing are probably because
a pointer ends up pointing into another pointer's domain. You're not
guaranteed to find it, but the buffer zones between allocations are of
course likely to catch at least some of the boundary issues.....

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136

Title:
  enblend creates an unexplainable black area.

Status in Enblend:
  Confirmed

Bug description:
  enblending       http://prive.bitwizard.nl/t80001.tif
  and                  http://prive.bitwizard.nl/t80003.tif
  results in          http://prive.bitwizard.nl/t8a.tif

  I cannot say I expected that black triangle in the output. My enblend
  was pulled from hg this morning (no changes) and built without
  imagecache or openMP. (imagecache causes corruption of the output
  similar but different to this. )

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/721136/+subscriptions