Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 28 Mar 2002 20:06:09 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: stacktrace from withn an exec upon error condition Message-ID: <20020329010609.GB19845@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020328153930 DOT GF11781 AT redhat DOT com> <20020328221751 DOT GK16757 AT redhat DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020328161017 DOT 0274f2c8 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.2.20020328161017.0274f2c8@pop3.cris.com> User-Agent: Mutt/1.3.23.1i On Thu, Mar 28, 2002 at 04:32:36PM -0800, Randall R Schulz wrote: >If you're going to take the time to respond, the least you could do is >give a useful answer. > >Since unlike Chris, I do not know the answer, I'll illustrate how I >discovered it. > >[snip] On Thu, Mar 28, 2002 at 05:17:51PM -0500, Christopher Faylor wrote: >I suggest that you write a simple test file and run it. That would >probably answer all of your questions. e.g., % cat > tst.c int main (int argc, char **argv) { cygwin_stackdump (); } ^D % gcc -o tst.exe tst.c % ./tst.exe (stack dump output) % ./tst.exe 2>/dev/null (no stack dump output) Since you seem to assume that I know the answer, one would have to wonder why you wouldn't try what I suggested before jumping through hoops. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/