X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL,TW_YG
X-Spam-Check-By:	sourceware.org
Message-ID:	<4EA9892A.6070708@cornell.edu>
Date:	Thu, 27 Oct 2011 12:39:06 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: gdb cygutils:/bin/mkshortcut.exe
References:	<1319721362 DOT 21467 DOT YahooMailClassic AT web120718 DOT mail DOT ne1 DOT yahoo DOT com>
In-Reply-To:	<1319721362.21467.YahooMailClassic@web120718.mail.ne1.yahoo.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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 10/27/2011 9:16 AM, Regid Ichira wrote:
>    I have a problem with /bin/mkshortcut.exe from the cygutils package.  It was mentioned here
> a few days ago.  The list archive has records of a similar problem from about a year and a
> half ago.
>    I am considering trying to run it under gdb.  I guess that the shortest way to add debugging
> symbols to the executable is to build the entire cygutils package without stripping it.
>    Is there a simpler way to add debugging information only to mkshortcut.exe?
> What packages are required?

/usr/share/doc/Cygwin/cygutils.README tells you what's needed to build 
cygutils.

An alternative to building cygutils would be to improve your original 
problem report so that you might be more likely to get help on this 
list.  For example, you wrote "By running those commands manually, I 
think the problem is the last, /bin/mkshortcut, line."  But you didn't 
say what happened when you ran that command manually.  You also didn't 
attach the cygcheck output requested at

   http://cygwin.com/problems.html

Ken

--
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 -