Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sun, 2 Jan 2005 17:01:03 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Stackdump trace - problem and patch
Message-ID: <20050102220103.GF20747@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <000901c4efdf$7e29f180$0200000a AT agamemnon> <20050101174825 DOT GB16231 AT trixie DOT casa DOT cgf DOT cx> <009c01c4f0fc$92f2b160$0200000a AT agamemnon>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <009c01c4f0fc$92f2b160$0200000a@agamemnon>
User-Agent: Mutt/1.4.1i

On Sun, Jan 02, 2005 at 01:55:03PM -0500, Jon A. Lambert wrote:
>Christopher Faylor wrote:
>>On Sat, Jan 01, 2005 at 03:54:23AM -0500, Jon A. Lambert wrote:
>>>my application.  I tried various means of examining and setting the
>>>registers in the stack to get to a frame that was within my app.  I
>>>have read the various messages on the list describing how to get to
>>>those frames.  It's rather tricky, and it availed me not.  Probably
>>>a personal problem. ;-)
>>
>>Probably.  And, for that reason we're not going to be adding another
>>cygwin option.  There is little reason to provide workarounds like
>>this when the real fix would be either to fix the user or the
>>application.
>
>Ah the user was looking to fix the application.  The difficulty I was 
>running into is identical to the scenario Robert Baruch posted here:
>http://www.cygwin.com/ml/cygwin/2003-12/msg01047.html

By application, I meant dumper.exe or gdb.exe in this scenario.

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