X-Spam-Check-By: sourceware.org Message-ID: <458FDA73.2000300@cygwin.com> Date: Mon, 25 Dec 2006 09:04:35 -0500 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061108 Fedora/1.5.0.8-1.fc4.remi Thunderbird/1.5.0.8 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb. References: <89c3ea2b0612242133o6dd57ef5x5a536490e0fd009f AT mail DOT gmail DOT com> In-Reply-To: <89c3ea2b0612242133o6dd57ef5x5a536490e0fd009f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 andy wang wrote: > Hi, All: > > now I get a new question: how to debug with the crash, especially > with the corrupt stack in multi-thread environment using gdb. > > I found a related post using "info reg, watch 0x2300000" such low > level command to trace a crash. > http://www.cygwin.com/ml/cygwin/2004-02/msg00921.html > > My question is where I can start? Can you please recommand some > articles or books or some tips? Thanks a lot. Download a snapshot with symbols so you get better stack info: Either that, or build cygwin yourself with debugging info so you can do the same and play with the source. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/