X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: Subject: RE: seg fault produces stackdump with no stack trace Date: Fri, 1 Aug 2008 16:35:12 +0100 Message-ID: <001e01c8f3ec$305ecdd0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 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/