2009/1/26 Lukáš Jirkovský <[email protected]>: > Hello, > something pushes me to find out what causes bug #2121647. > > So here are the latest news. > > Problem begins in > CachedFileImageIteratorBase::operator*() > - which is trying to access > vigra::TinyVectorBase<unsigned char, 3, unsigned char [3], > vigra::TinyVector<unsigned char, 3> > > - problem is that _data is not in memory (I can't even access it > from debugger). > > Does anyone know what may cause this? I've read ISO/IEC 14882/2003 > standard and I've not found anything which would allow this behavior. > IMO data should be accessible everywhere it is (if it's in stack or > heap, RAM or swapped) with exception of CPU register (in which case > compiler shouldn't allow this data to be stored there). >
I've found something really strange. If enblend is compiled with --enable-debug=yes or with other known workaround the currentRow in CachedFileImageIteratorBase::operator*() is ordinary array (I don't know the type but I think it's unsigned char (and it contains 0 '\0')). But when I use segfaulting version it seems that currentRow is defined as vigra::TinyVectorBase<unsigned char, 3, unsigned char [3],> vigra::TinyVector<unsigned char, 3> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
