DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=xHrxlC8SHuX32UFIOaqc2vzodTeQm1Pthm0MFygcePJr1JuhpbDKZ
	jRAg2XHqOa6P3/SFMr3fA61hdH2MdnFfBvF2FXsU7gkUyv4wdHQgIsRMhy+ocN71
	DH6C4d8nhBXBxeDC3uYP+2SIExj/tbV8RkW3eqo9z23vBrir2eL9TA=
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: Mon, 31 Mar 2014 12:19:15 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: exe.stackdump is always empty
Message-ID: <20140331101915.GC23383@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5F8AAC04F9616747BC4CC0E803D5907D0C8A8F7F AT MLBXv04 DOT nih DOT gov>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="TYecfFk8j8mZq+dy"
Content-Disposition: inline
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C8A8F7F@MLBXv04.nih.gov>
User-Agent: Mutt/1.5.21 (2010-09-15)

--TYecfFk8j8mZq+dy
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 29 05:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Hello List,
>=20
> I wonder, if there any special setup was necessary to make coredumps non-=
empty.
>=20
> When my program crashes it leaves only the following:
>=20
> Stack trace:
> Frame     Function  Args
>=20
> despite is was built and linked with -g (so should have all the debugging=
 info
> intact).  I did not modify any shell limits from their stock values, eith=
er.
>=20
> $ ulimit -a
> core file size          (blocks, -c) unlimited
> data seg size           (kbytes, -d) unlimited
> file size               (blocks, -f) unlimited
> open files                      (-n) 256
> pipe size            (512 bytes, -p) 8
> stack size              (kbytes, -s) 2025
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 256
> virtual memory          (kbytes, -v) unlimited
>=20
> Any insight will be greatly appreciated.

If your process crashes with a thoroughly scrambled stack, there's
a good chance that Cygwin won't be able to create a stackdump file
because it crashes again while producing the stackdump.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--TYecfFk8j8mZq+dy
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTOUEjAAoJEPU2Bp2uRE+gSFwP/3aqKKuBmVPG0Iz6/7M/qgUI
qegJI9isgKoM53A6HMtXGzoyQHsKp6MnTBrSWi4JX12bDBPvC/YrM8GWTDa0FR6X
JeBrZaHxj+dSA7I4Zbc2uwn0VDyP9DJvJ5Hu599o0xcFpzHldac3J1/zltKTMh+l
UCCNDfN4CUFV9WnofPf3KbhDpORbD8pHG3Mi2fd2plS4kQJN/8NVZzXKx7qyXHRa
02/ZIduH/l55ZkNtx+8EMRVwtSPXGmfO3XcyCo+Wru7WbY7mm37HCoVXqFEeESjF
K9DuHiXimvBVm+IXv/sXayww9umAiXQrrfEPVgPf3Q2zn4Yx/T7LxtemYli99O9/
UDoQF9uWDUdTkJ+Wl6oW6L2CcaQzAHLy81Au65o6hEHtV/YG+g0I3N5hSVWNTUnm
gZ7n1E0bqwoZAbg0c4LiqgAt/HTAV5Vznt8vHU7zGmLDbcP80e66wlsBCPiqQfKt
WIrH6YB29oe4ssLfG++GxL+Aa3ea4d7yJkJkwZeO4Vk0+QUqbEHanDzE5lFYP9zs
1gnzQf913LW9JdpA6FtAh5cDeiKbreDUrjn+QYuOzvJcTBMezmQbYE+1FB79v68V
nFUaIWrTfjqcv/P7SkYKEraW98cdnTpQXuPeVRfB0NgzDWYSJNhZThcgW57VmzYp
3qZsP1LNjTRu+AHDtpXH
=yOgE
-----END PGP SIGNATURE-----

--TYecfFk8j8mZq+dy--