X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=lC9/deCzXl/k5vUXSx1eP+DnLeIHZV74oJdynXZWP1L
	kaGatx9jkQ35cJUk3DrfMX5I5WmsUfQoB/08+9Dr1ViJ7oJzlzF2LhYOl8y4Mm8b
	j0ckCFy4LGruUHo6wM1nVnYQfmRxCkyr77SbuHNPf+Lzqry02fUk8FMFjVxxCwek
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=ayS+1bA+ybqVMtKc0FRDiGxmM6c=; b=Q+OLN5xlU0eisQkPQ
	VpXt/MyGI0y87G4a0W12PEulxzAuZUyeGKr9Yd+lkYJlmwN9qUe792CREUNDVB9u
	T3rZM8chUyZkVVKGT4ChIxn9v72psIiZg9aenN+Mf14LE2R2Ju1QeI5+1f3L4/CG
	14Sxzyt7IQslqwI9SgFSnw2Es8=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ig0-f170.google.com
X-Received: by 10.107.4.66 with SMTP id 63mr16930738ioe.48.1421418474623;        Fri, 16 Jan 2015 06:27:54 -0800 (PST)
From: "cyg Simple" <cygsimple AT gmail DOT com>
To: <cygwin AT cygwin DOT com>
References: <CABsQ44Z6c3Y9xwMepP7cmf94jD4MLNc+RUyDNKunAYB8y2irgw AT mail DOT gmail DOT com>
In-Reply-To: <CABsQ44Z6c3Y9xwMepP7cmf94jD4MLNc+RUyDNKunAYB8y2irgw@mail.gmail.com>
Subject: RE: Stack Dump Message
Date: Fri, 16 Jan 2015 09:28:09 -0500
Message-ID: <00d901d03198$a83e9c90$f8bbd5b0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="UTF-8"
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t0GESDpX023931

> From: Ameen Sayegh
> 
> hello there,
>
> I already asked the question on [stack
> overflow](http://stackoverflow.com/q/27943489/2318073) but I didn't quite get
> the answer I want.
>

Why make us look?

<quote>
I'm using Cygwin to compile my C programs

I created a program that will call abort whenever an error occurs.

when I run the program from Cygwin Terminal the function produces the following output:

Aborted (core dumped)
but If I run the program from Windows CMD or Explorer it produces the following:

      0 [main] test 1904 cygwin_exception::open_stackdumpfile: Dumping stack trace to test.exe.stackdump
Can I change the message to the first format? How?

because the second format is very ugly and I can't tell if this is a bug in the program (e.g: Access Violation, Divide By Zero,...) or the abort function>

and why do I get different messages even though the build is the same?

Note: Please, Don't tell me not to use the abort function or the Cygwin compiler
</quote>

 
> Here is the issue:
> abort function produces the output
>     "Aborted (core dumped)"
> when I run the program on cygwin terminal while it produce
>     " 0 [main] test 1904 cygwin_exception::open_stackdumpfile: Dumping stack
> trace to test.exe.stackdump"
> when I run it on Windows CMD or Windows Explorer. Why is that? and Can I
> change it to the first format?
> 

Different runtime environments are likely to do different things; the likely difference is that Windows doesn't understand the signal of the SIGABRT and Cygwin does.


> I can't read the source code to figure out what exactly is going on because such
> projects are bigger than my skills but I tried though and I found that the abort
> function is sending SIGABRT signal but couldn't find the signal handlers I hope
> someone will help me with this.

Not likely to change; this isn't something that we should care about.

--
cyg Simple




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