Thanks for the input Yuval.  DEP reports a buffer overflow exception
as the reason for closing Hugin.  And, I did build on the same
platform having the issue.  I did not create an installer, simply ran
the executable from INSTALL/FILES/bin.

The older versions started with 0,7,0,3405.

I shall run the version you reference and report back.

--
Howard

On Jul 1, 12:11 pm, Yuval Levy <[email protected]> wrote:
> Hi Howard,
>
> hbl wrote:
> > Hugin has been closing unexectedly on 'load images'.  The cause is
> > Microsoft Data Execution Prevention service.
>
> <http://en.wikipedia.org/wiki/Data_Execution_Prevention>
>
> from your description it looks like we have some kind of overflow /
> memory management issue.
>
> when you are saying that this is commont to all versions since 7.0, does
> this include 7.0 or not?
>
> I understand you have been able to build Hugin on your Toshiba notebook
> that is experiencing the DEP issue? would you help find out where the
> error is located and when it was introduced?
>
> For a starter, can you confirm that
> <http://sourceforge.net/project/downloading.php?group_id=77506&filenam...>
> works properly by removing / uninstalling completely any other version
> and installing / running this one?
>
> Next, can you try to check out SVN 3422 (which is more or less
> equivalent to 0.7.0) and build it on your box?
>
> If the 0.7.0 installer works and the SVN3422 crashes, then the issue is
> with the SDK on your box and we can continue looking for the fault from
> from there.
>
> Yuv
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to