This is the mail archive of the
mailing list for the Cygwin project.
RE: Exception: STATUS_PRIVILEGED_INSTRUCTION occurs before main is executed.
- From: "Bruce Adams [TEPG Sunbury]" <bruadams at tycoint dot com>
- To: <cygwin at cygwin dot com>
- Cc: "Max Bowsher" <maxb at ukf dot net>
- Date: Thu, 6 Mar 2003 16:57:08 -0000
- Subject: RE: Exception: STATUS_PRIVILEGED_INSTRUCTION occurs before main is executed.
>From: Max Bowsher [mailto:maxb at ukf dot net]
>Sent: 06 March 2003 14:43
>To: cygwin at cygwin dot com
>Subject: Re: Exception: STATUS_PRIVILEGED_INSTRUCTION occurs
>before main is executed.
>> On Thu, 6 Mar 2003, Bruce Adams [TEPG Sunbury] wrote:
>>> I think it would be a great idea if the post setup phase did some
>>> basic configure style checking (assuming it doesn't already). i.e.
>>> Checking if the compiler gcc works.... No
>>> It would have saved me a couple of months of heartache.
>>> I seems very strange that nobody else spotted it though.
>>> How exactly could an installation become so corrupt that nothing
>>> short of a complete download (from a different mirror site)
>>> without the underlying package being in error?
>Somehow, it managed it, since there are lots of us who haven't
>done a clean install for ages.
>Igor Pechtchanski wrote:
>> I'm reasonably sure that if you create such a post-install
>> will be at least thoughfully considered by the gcc maintainer...
>Well, I'm not the gcc maintainer, but I'd be surprised if such
>a script was accepted. Here's why:
>1) There is no (good) way for a postinstall script to talk to the user.
Is that a limitation of the current postinstall process? I'm not sure
what your definition of 'good' entails.
A report that doesn't explain the problem is better than no report at all.
For a first cut I'd be happy with
tk_messageBox -title "Installation Error" -message "Problem with C++
Though something more like the below would be preferable for the general
Gcc post install
Add error to list
Post post install :-)
print list of errors found to console
ELSE // gui-based-install
print list of errors found to message box instead of "installation ok"
>2) If the package was broken immediately after installation,
>then wouldn't the maintainer have noticed before releasing it?
One would hope so. But if they did it was not enough to spot my dodgey
installation problem. Anyway, does it ever hurt to double check?
We wouldn't have to run the complete gcc test-suite (though as an option
it might be nice). Just a smoke-test of some reasonably simple code.
It wouldn't be such a bad thing if all packages had one, especially
Any opinions expressed in this e-mail are those of the individual and not
necessarily those of Tyco Safety Products.
Any prices for the supply of goods or services are only valid if supported
by a formal written quotation.
This e-mail and any files transmitted with it, including replies and
forwarded copies (which may contain alterations) subsequently transmitted
from Tyco Saftey Products are confidential and solely for the use
of the intended recipient.
If you are not the intended recipient or the person responsible for
delivery to the intended recipient, be advised that you have received this
e-mail in error and that any use is strictly prohibited. In this event,
please notify us via e-mail at 'helpdesk dot tepg at tycoint dot com' or telephone on
0121 255 6499 and then delete the e-mail and any copies of it.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html