This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: seg fault produces stackdump with no stack trace
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Fri, 1 Aug 2008 16:35:12 +0100
- Subject: RE: seg fault produces stackdump with no stack trace
- References: <loom.20080801T151340-446@post.gmane.org>
Steve Waldo wrote on 01 August 2008 16:24:
> When my app gets a seg fault it produces the expected stackdump file:
>
> [1]- Segmentation fault (core dumped) ./ResourceMgr
>
> but the resulting file contains no stack trace:
> Is there a setting I'm missing somewhere?
Nah, it probably just means the stack was too badly trashed to backtrace
successfully. You're probably best off trying it under gdb.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/