This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb.
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 25 Dec 2006 09:04:35 -0500
- Subject: Re: how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb.
- References: <89c3ea2b0612242133o6dd57ef5x5a536490e0fd009f@mail.gmail.com>
- Reply-to: 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:
<http://cygwin.com/snapshots/>
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/