Howard,
I've enabled DEP on my system, and the programs I know to have
trouble do properly report BEX errors, so I know DEP is getting raised
appropriately. I've also confirmed with wmic that all the settings reflect
its enabled, with a value of True, 3, as you did.
I went ahead and built a binary based on the latest SVN (for native
x64), through the full build process, including the installer. I opted for
x64 since, as noted in the Microsoft KB article and the prior e-mail, always
good to match platform and application.
I've tried several scenarios, loading old projects, TIFFs and JPGs,
etc, and had no problem. Certainly, there are a lot of variables at play
here, so it may take some time to isolate. In the mean time, I'd suggest
following Yuval's directions of trying the last 'certified' version, in
attempt to find the basement on when this issue might have first been
introduced. This should be fairly easy and non-invasive.
What I'd like to try as a next step, as a means of hopefully getting
more information, is getting a crashdump from you when a DEP error has been
raised.
It's been a while since I've had to do it by hand (tend to use
API-based hooks to catch when an application crashes), so I hope you'll bear
with me if I direct you down the wrong path once or twice. Since you
mentioned Vista, the following KB article may help:
http://support.microsoft.com/kb/931673
Since I don't have the symbols Ad used for his installer, I'll be
mailing you off-list a 32-bit based version on the latest SVN that I'll
compile locally. This will ensure I have the necessary debug symbol files to
wind through the stack. If this is a concern for you, we can work off-list
on directing the necessary compilation steps, just be aware that it's not
uncommon for symbols to reach hundreds of megs for large projects.
Once you've gotten the new setup binary and everything is installed,
when you get an application crash (eg: due to DEP), see if you can follow
the directions of Method 1 as a means to intercept the crash. Once you have
that crash (located in the path specified), can you attach it and e-mail it
to me off-list? I'm not sure the default settings of Vista for creating
crashes, but a simple Crashdump of Notepad is around 50 megs. If it's too
large to e-mail, we can work off-list on a transfer mechanism. By all means,
compress compress compress! If you're unable to generate a crashdump once
it's raised a DEP error, let me know, and I'll see further if I can
investigate.
For those following on-list, especially Bruno, if a final 'formal'
Win32 build is released, it might help to keep the symbol files around.
Certainly users can build their own binaries, preserve the symbol files, and
debug themselves, but given how most Windows users aren't necessarily handy
with compiling and debugging their software, it may be helpful for some of
the weird bugs that remain post-release (as I recall, there are a few
mystery ones out there affecting Windows users)
Ryan
> -----Original Message-----
> From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On
> Behalf Of hbl
> Sent: Wednesday, July 01, 2009 9:02 PM
> To: hugin and other free panoramic software
> Subject: [hugin-ptx] Re: hugin installer for Windows Vista SVN 3975
>
>
> Thanks for checking in, Ryan. My notebook has the 32-bit version of
> Vista Home Premium. I suspect hardware detection is on as I have
> turned off sw detection using bcdedit.
>
> On hardware enforcement, I get True, 3.
>
> On Jul 1, 7:38 pm, <ryan+hu...@sleevi.com> wrote:
> > Howard,
> >
> > Would you mind
> checkinghttp://support.microsoft.com/kb/912923and
> > reporting back a bit more about the values from WMIC?
> >
> > I'm hoping to identify:
> > 1) Are you using hardware-enforced DEP?
> > 2) What the current value is for the Windows
> enforcement of
> > it
> > 3) Any possible hardware switches (Note the last line
> of
> > Method 1)
> >
> > In addition to the information wmic will provide, can you
> also tell
> > me:
> > 1) Which mobel Toshiba laptop (Trying to understand
> > processor architecture)
> > 2) What version of Windows you're running (Full
> version
> > string of major/minor/build + 32 bit or 64-bit)
> >
> > If I followed the thread correctly, I understand you can and
> have
> > compiled your own versions. If you are running on a 64-bit platform
> with a
> > 64-bit OS, are you compiling 64-bit Windows binaries or the default
> 32-bit
> > ones? I'm suspecting based on your description that you're on 32-bit
> and
> > running 32-bit, I just wanted to make sure, since DEP can get weird
> when
> > there are mismatches.
> >
> > To be fair, DEP has caused me more headache than it's worth,
> simply
> > because the sheer number of buggy programs out there. It's a trade-
> off
> > between hard crashes (because of the NX bit being triggered) or soft
> crahses
> > + potential security holes (to be fair, not every buffer
> under/overrun
> > represents an exploitable security hole, and surprisingly some
> systems can
> > 'gracefully' recover, even if they're still buggy in the first
> place).
> >
> > While you're doing that, I'll flip on hardware DEP on my
> Vista x64
> > machine and see if I can reproduce with the native x64 binaries I've
> been
> > compiling for my own environment. I know it's probably not a 1:1
> mapping of
> > your problem, but hopefully if it is some bug in Hugin, it'll surface
> there
> > as well.
> >
> > Thanks,
> > Ryan
> >
> > > -----Original Message-----
> > > From: hugin-ptx@googlegroups.com [mailto:hugin-
> p...@googlegroups.com] On
> > > Behalf Of hbl
> > > Sent: Wednesday, July 01, 2009 7:43 PM
> > > To: hugin and other free panoramic software
> > > Subject: [hugin-ptx] Re: hugin installer for Windows Vista SVN 3975
> >
> > > Rick, when I try that option, the OS refuses stating that Hugin
> must
> > > run under DEP.
> >
> > > On Jul 1, 6:15 pm, RueiKe <ruei...@yahoo.com> wrote:
> > > > For Windows Vista, there is an option under "System Properties" -
> >
> > > > "Performance Options" to change the settings of DEP. On my
> system,
> > > it
> > > > was set to be enable for essential Windows programs only. When I
> > > > change it to be active for all programs, I sitll don't see it
> raising
> > > > any DEP error for hugin. I am running 64bit, SP1, so maybe SP2
> is
> > > > more sensitive.
> >
> > > > Seems like I am the only one reporting major issues in not being
> able
> > > > to use anything newer than SVN3884 for large projects. Are there
> > > > others using the latest builds on windows for large projects with
> no
> > > > problems?
> >
> > > > Regards,
> > > > Rick
> >
> > > > On Jul 2, 6:40 am, Bruno Postle <br...@postle.net> wrote:
> >
> > > > > On Wed 01-Jul-2009 at 18:32 -0400, Yuval Levy wrote:
> >
> > > > > >The big question is whether to release 0.8 before this bug is
> > > fixed, or
> > > > > >keep postponing 0.8. For users that are not affected by this
> bug,
> > > the
> > > > > >current snapshot is good enough for a release...
> >
> > > > > Yes, I'd like to go with the current release candidate, but I'm
> not
> > > > > sure if these problems are in hugin, the windows build, windows
> > > > > itself or some 3rd party windows software.
> >
> > > > > Does anyone else see these crashes on OS X or Linux? (note
> that
> > > > > enblend or enfuse crashing during stitching isn't a hugin bug)
> >
> > > > > --
> > > > > 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@googlegroups.com
To unsubscribe from this group, send email to
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
