hugin installer for Windows Vista SVN 3975

[Yuval Levy-6]

Hi Ryan,

ryan+hugin@... wrote:
> To be fair, DEP has caused me more headache than it's worth, simply
> because the sheer number of buggy programs out there.

in this case DEP may prove to be a debugging tool :)

honestly I don't think that researching DEP is of any help in his
context. If DEP had not caught the buffer overflow, it may have gone
unnoticed for a longer while. We have an issue to take care of in the
Hugin codebase or in an SDK component. Once it will be fixed it won't be
relevant to DEP anymore.

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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Yuval Levy-6]

Hi again, Ryan,

Ryan Sleevi wrote:
> I went ahead and built a binary based on the latest SVN (for native
> x64), through the full build process, including the installer.

this means that you also built enblend-enfuse? autopano-sift-c? libpano?
wxwidgets? and all the other SDK components? for native x64? it would be
nice if you could contribute documentation of the process so that we can
release an x64 "official" version as well.

we had a case recently when enblend-enfuse built with debug symbols
would work while stripped of them it would crash - the debug symbols
were just enough "padding" for the overflow not to do too much damage. I
hope this is not the explanation for why your build does not crash.

On the other hand, it could be that the bug is in the updated SDK. Would
have to take the old SDK, re-build the old wxWidgets to support the
GLCanvas and try a recent Hugin SVN against it...

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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Harry van der Wolf-3]

Hi all,

I googled on "Toshiba Vista DEP" and found more hits on similar issues. It might be a Toshiba issue, not a Hugin issue.

Harry

2009/7/2 Yuval Levy <google@...>

Hi again, Ryan,

Ryan Sleevi wrote:
>       I went ahead and built a binary based on the latest SVN (for native
> x64), through the full build process, including the installer.

this means that you also built enblend-enfuse? autopano-sift-c? libpano?
wxwidgets? and all the other SDK components? for native x64? it would be
nice if you could contribute documentation of the process so that we can
release an x64 "official" version as well.

we had a case recently when enblend-enfuse built with debug symbols
would work while stripped of them it would crash - the debug symbols
were just enough "padding" for the overflow not to do too much damage. I
hope this is not the explanation for why your build does not crash.

On the other hand, it could be that the bug is in the updated SDK. Would
have to take the old SDK, re-build the old wxWidgets to support the
GLCanvas and try a recent Hugin SVN against it...

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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Ryan Sleevi]

I did update documentation of the process.

http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29

and

http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29_Patches


The "downside" to the current process is it requires two sets of
SDKs/wxWidgets/etc. The sheer impact of being able to get side-by-side
libraries (eg: ilmbase.x64.lib and ilmbase.x32.lib) and all the project
settings were way more headache and heartache than I wanted to invest during
the weekend that I worked on getting everything running, although that is
the logical next step.

I'm working on updating the patch set mentioned on the patch pages, as it
looks like there was one bit of patch trouble with libpano, although it was
resolved in < 5 minutes. Other than that, the directions are still valid and
can be done from scratch, as I went through everything again last night when
setting up the x32 build for Howard.

I've definitely seen benefits to the x64 version - Most notably on
autopano-sift-c, as I'm able to throw my larger projects at it and have it
go well into the 7-8 gig range on my system generating control points,
rather than having to manually break things into chunks. Of course, it
sounds like the future work on getting rows/columns setup and optimizing how
CP generation gets done will resolve that.

Lately I've been working on getting profile-guided versions of
enblend/enfuse/hdrmerge and the other 'heavy lifters' of the Hugin stack,
and have been seeing performance gains on an order of 10-25%. Quite handy on
the large projects.

In the enblend-enfuse case, are you talking about a debug binary or a
release binary with debug symbols? In the case of Windows, debug symbols are
stored in a separate file (.pdb), which makes it easy to ship "Production"
exes (with no debug code/memory address alterations/etc), but when crashes
occur, be able to load the symbols and correlate the lines/files/etc.
Optimizing compilers can naturally make this harder, but my experience with
.pdb's is that it's fairly accurate. Using the Intel Compiler chain, which
can perform much more rigorous (and intelligent) optimizations, it does get
harder to make both "screaming awesome" and "debuggable", but it's not
impossible. I was just proposing that the .PDBs be preserved (for the SDK
and for Hugin itself) when a release is made, possibly on the project file
store, and that way anyone with Visual Studio (including the Express
Editions, IIRC), would be able to load those up and step through the
crashes.

As for the SDK, like I mentioned, everything was built by hand from scratch
following the directions on that page, which AFAIK is how Ad is building
his, so we'll see. Hopefully Howard will have more information using the
build I provided him, and we'll be able to get to the bottom of this.

>
> Hi again, Ryan,
>
> Ryan Sleevi wrote:
> > I went ahead and built a binary based on the latest SVN (for
> native
> > x64), through the full build process, including the installer.
>
> this means that you also built enblend-enfuse? autopano-sift-c?
> libpano?
> wxwidgets? and all the other SDK components? for native x64? it would
> be
> nice if you could contribute documentation of the process so that we
> can
> release an x64 "official" version as well.
>
> we had a case recently when enblend-enfuse built with debug symbols
> would work while stripped of them it would crash - the debug symbols
> were just enough "padding" for the overflow not to do too much damage.
> I
> hope this is not the explanation for why your build does not crash.
>
> On the other hand, it could be that the bug is in the updated SDK.
> Would
> have to take the old SDK, re-build the old wxWidgets to support the
> GLCanvas and try a recent Hugin SVN against it...
>
> 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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Ryan Sleevi]

Only if you like debugging Windows ;)

What I meant by DEP being more headache is that there are any number of
reasons that DEP can be triggered independent of Hugin, so it may not be a
legitimate bug.

An example to illustrate this (with all of its frustration) is some recent
heartache I had with a certain laptop manufacturer that sounds like "Bell"
and the drivers they supplied for the built-in biometric device. The
"security functions" of the drivers ended up hooking into several Windows
API calls for filesystem access (yes, you can do this, and there are a
number of legitimate reasons - most popular being anti-virus/security
products). Unfortunately, these drivers had a bug (if we count "suck" as a
bug) and it had a huge negative impact on my system performance.

Compiling one of the projects I work on, which has thousands of files and
hundreds of thousands LOC took almost 100x longer than normal, and
eventually failed, because there was a leak in the drivers. A quick
uninstall, and my system was back to screaming performance.

Consider then, the situation if these drivers had a buffer underrun/overrun.
In Windows, the DEP exception would be triggered, and it would work its way
up to the stack, finally into the application that made the OS call (which
it didn't know was being hooked by the buggy app). That app would then
terminate, with the user being told it was that app that was buggy.

I wish I could say situations like this are uncommon, but I see regularly
applications that instill themselves into critical locations (shell
handlers, API hooks, control panel drivers) that are buggy, and because of
how the exception works its way up the chain, it ends up crashing a
perfectly benign application (as it cannot control for those crashes).

That's just the frame of mind I'm in with regards to researching this, is
that past experience, especially with DEP, by no means signifies a bug in
Hugin necessarily. While still worth investigating, I would not think this
bug (especially with the difficulty reproducing) should be considered a
'block' in any means.

Cheers,
        Ryan

> -----Original Message-----
> From: hugin-ptx@... [mailto:hugin-ptx@...] On
> Behalf Of Yuval Levy
> Sent: Thursday, July 02, 2009 4:01 PM
> To: hugin-ptx@...
> Subject: [hugin-ptx] Re: hugin installer for Windows Vista SVN 3975
>
>
> Hi Ryan,
>
> ryan+hugin@... wrote:
> > To be fair, DEP has caused me more headache than it's worth,
> simply
> > because the sheer number of buggy programs out there.
>
> in this case DEP may prove to be a debugging tool :)
>
> honestly I don't think that researching DEP is of any help in his
> context. If DEP had not caught the buffer overflow, it may have gone
> unnoticed for a longer while. We have an issue to take care of in the
> Hugin codebase or in an SDK component. Once it will be fixed it won't
> be
> relevant to DEP anymore.
>
> 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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[hbl]

Harry, I think Toshiba has less to do with the issue than the OS.  DEP
depends on both hardware and software flags.  Both are supplied by
parties outside Toshiba.  I have no doubt a buffer overflow is being
detected.  And, as I recall, this, many yarns ago, was the very first
attack on an OS:  The password buffer was 256 bytes long.  After that,
bogus passwords overwrote critical code space.

But, why now?

Looking at the history file, there have been unexplained closures of
more than hugin or GIMP; Windows Explorer also was in the list.
Presumably, closed by the hardware flag because I don't recall seeing
a message from DEP.  Perhaps the latest Windows OS update improved the
software DEP with the notification message from the system tray.  Just
conjecture...

We shall persist until a solution is identified.  Thanks to you all
for your participation.

On Jul 2, 3:36 pm, Harry van der Wolf <hvdw...@...> wrote:

> Hi all,
>
> I googled on "Toshiba Vista DEP" and found more hits on similar issues. It
> might be a Toshiba issue, not a Hugin issue.
>
> Harry
>
> 2009/7/2 Yuval Levy <goo...@...>
>
>
>
> > Hi again, Ryan,
>
> > Ryan Sleevi wrote:
> > >       I went ahead and built a binary based on the latest SVN (for native
> > > x64), through the full build process, including the installer.
>
> > this means that you also built enblend-enfuse? autopano-sift-c? libpano?
> > wxwidgets? and all the other SDK components? for native x64? it would be
> > nice if you could contribute documentation of the process so that we can
> > release an x64 "official" version as well.
>
> > we had a case recently when enblend-enfuse built with debug symbols
> > would work while stripped of them it would crash - the debug symbols
> > were just enough "padding" for the overflow not to do too much damage. I
> > hope this is not the explanation for why your build does not crash.
>
> > On the other hand, it could be that the bug is in the updated SDK. Would
> > have to take the old SDK, re-build the old wxWidgets to support the
> > GLCanvas and try a recent Hugin SVN against it...
>
> > 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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Thomas Steiner]

> Please find a new hugin installer for Windows Vista based on SVN revision
> 3975 athttp://hugin.huikeshoven.org/

when the program loads, it says Version "3966", although the about
screen is correct.
thomas

--~--~---------~--~----~------------~-------~--~----~
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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Yuval Levy-6]

Ryan Sleevi wrote:
> I did update documentation of the process.
>
> http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29
>
> and
>
> http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29_Patches

did I thank you? THANK YOU, Ryan!

I've linked the pages from
<http://wiki.panotools.org/Development_of_Open_Source_tools#Supported_Platforms>

and with you and your expertise around I allowed myself to note that
64bit Windows is now supported.

Will you contribute a 64bit installer of 0.8.0 final after Bruno
released it?

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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Ryan Sleevi]

> and with you and your expertise around I allowed myself to note that
> 64bit Windows is now supported.

Well, it's only supported if those two patch sets get merged upstream prior
to 0.8 (your prior e-mail asking for thoughts). My belief is they should be
very minor (the patches to Hugin itself, really Vigra, were straight from
upstream just backported).

The patches to the supplementary products are (more or less) just patching
the solution files, although other projects that use Vigra had a few changes
applied to them as well. I'll try to update the libpano .sln patch (part of
the second set), since I found I missed something with x64 on it.

> Will you contribute a 64bit installer of 0.8.0 final after Bruno
> released it?

With regards to the installer itself, my process has not been clean. I get
several errors with the .iss that I haven't bothered to look deeper into.
Mostly issues with matchnsift/matchpoint/perl files being missing. I haven't
bothered to look into this, because it hasn't affected my personal usage,
but it would be a hindrance towards a 'proper' release. The other part is
still my own personal concern regarding the patented code and compiling it -
being an American and all. The whole distinction of direct and indirect
infringement is a point of concern.

As to the steps/compilation themselves, the process can be fully
accomplished with Microsoft's free-as-in-beer toolchain. The x64 compilers,
while not native to the Visual Studio 2008 Express Edition, can be obtained
from the Windows Platform SDK 6.1 and native x64 binaries compiled (or
cross-compiled, for those on x32). Using the Express Edition requires one
extra step (as documented at
http://jenshuebel.wordpress.com/2009/02/12/visual-c-2008-express-edition-and
-64-bit-targets/ ), but otherwise, compilation should prove quite smooth.


--~--~---------~--~----~------------~-------~--~----~
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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Bruno Postle]

On Tue 07-Jul-2009 at 14:38 -0400, Ryan Sleevi wrote:
>
>Well, it's only supported if those two patch sets get merged upstream prior
>to 0.8 (your prior e-mail asking for thoughts). My belief is they should be
>very minor (the patches to Hugin itself, really Vigra, were straight from
>upstream just backported).

Sorry these didn't get applied, I'm trying not to break anything
that is currently already working and 64bit Windows is a new feature
rather than a bugfix (this shouldn't stop anyone creating a 0.8.0
64bit binary installer, they will just have to patch first).

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[RueiKe]

I have spent a few days with Ryan's 64bit build of hugin, and I think
"wow!" is the best way to summarize the experience so far.  Here are a
few observations:

I set the memory usage for enfuse and enblend to 7GB.  Both went upto
the limit while stitching a large project with no issues.  I also
noticed nona got upto about 5GB and hugin itself got to 3GB, even
though I had the image cache set to 500MB.

A 17k wide 360x180 blended/enfused equirectangular projection from
125, 70MB, 16bit TIFF files stitched in 72min!  Previous projects took
about 5hrs.

I tried one autopano-sift-c test case  for 15 images with --maxdim
4000 set and it found over 3000 control points.  Typically, I have
found the previous versions have issues adding control points when --
maxdim is set to > ~1200. I also tried adding a Nadir with these
settings, and ~10 control points were found for all adjacent images,
which never happened in previous runs.

The optimizer really didn't seem much faster.  Still only used about
12% of cpu resources.

Overall hugin interface was a bit perkier, especially when dealing
with control point editing and cropping.

Both preview windows were more responsive.  I had issues with every
previous build where I would get a boost thread resource error about 1
in 5 times when adjusting the projection in the regular preview
screen.  For this build, I could not make it crash!

Not a single crash since I started testing on large projects!  At
times, I have had a project active over days, without closing or re-
starting.

Definitely a much improved user experience for large projects.  It
looks like from the discussion threads that not many people in the
user community are dealing with such large projects, but that is all I
work with.  This build certainly makes that work more pleasant!  I
understand that it should not be critical path for 0.8.0, but it would
be a great enhancement for the next release.

Regards,
Rick

On Jul 8, 5:17 am, Bruno Postle <br...@...> wrote:

> On Tue 07-Jul-2009 at 14:38 -0400, Ryan Sleevi wrote:
>
>
>
> >Well, it's only supported if those two patch sets get merged upstream prior
> >to 0.8 (your prior e-mail asking for thoughts). My belief is they should be
> >very minor (the patches to Hugin itself, really Vigra, were straight from
> >upstream just backported).
>
> Sorry these didn't get applied, I'm trying not to break anything
> that is currently already working and 64bit Windows is a new feature
> rather than a bugfix (this shouldn't stop anyone creating a 0.8.0
> 64bit binary installer, they will just have to patch first).
>
> --
> Bruno

--~--~---------~--~----~------------~-------~--~----~
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 hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---