X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-5.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<CAAcBW0xJ0gA7tgEWUsFOahPtFPWoOxHPPE1DBKjxoNWf0=3SHA@mail.gmail.com>
References:	<CAAcBW0xWXFgUvm4bKYW8KtDWSXX5_GbamjQNOjKWLGFoXsfDCg AT mail DOT gmail DOT com> <CA+sc5mmKdBotzCPJTu4-QTpMtKUo4aMZoGPQQLEhOJ7vwEY+9Q AT mail DOT gmail DOT com> <CAAcBW0xJ0gA7tgEWUsFOahPtFPWoOxHPPE1DBKjxoNWf0=3SHA AT mail DOT gmail DOT com>
Date:	Mon, 10 Sep 2012 08:54:57 -0400
Message-ID:	<CA+sc5mn0L_E_WvLmxU0o+3GRb_81vsF1WPPc4N9VBfY4LyyGmQ@mail.gmail.com>
Subject:	Re: (core dumped) mkshortcut
From:	Earnie Boyd <earnie AT users DOT sourceforge DOT net>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Mon, Sep 10, 2012 at 7:02 AM, Robert Mark wrote:
> Hi Earnie,
>
>>> As per a previous message
>>> (http://cygwin.com/ml/cygwin/2012-05/msg00215.html) I am still finding
>>> that mkshortcut causes core dumps (Windows 7, 64 bit). I have tried a
>>> few different options: -P or -D still cause dumps. I have checked
>>> permissions and they are all ok. Some folders do cause the error, some
>>> don't.
>>>
>>> mkshortcut -n "I for cygwin bin" /D/cyghome/bin
>>> /home/RobertMarkBram/bin/createWindowsShortcut.sh: line 160:  8128
>>> Aborted                 (core dumped) mkshortcut -n "$shortcutName"
>>> "$target"
>>
>> I'm going to guess but have no fact to back it that the reason is due
>> to the fact you're executing in a 32bit environment and the shortcut
>> the tool makes needs a 64bit enviroment.  This may only be resolved by
>> a 64bit version of Cygwin.
>
> I did say I was running 64bit Win 7, so what exactly do you mean?
>

I mean that Cygwin at the moment is a 32 bit application.  So you are
executing in an emulation mode and some things might just not work as
expected.

> Cygwin.com says "The Cygwin DLL currently works with all recent,
> commercially released x86 32 bit and 64 bit versions of Windows".
>

It works but might not be able to do everything that is required due
to the limitations of the emulated environment.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -