how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb.

[Larry Hall (Cygwin)]

<http://cygwin.com/acronyms/#TOFU>.  Reformatted.

andy wang wrote:
>> 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.
>>
> Thanks .Larry!
> 
> If the bug is not in the cygwin1.dll but an application and with stack
> corrupted, how can I using the low level debug technics to find the
> reason.


The most common way is to put a breakpoint in the code before you get the
stack corruption and step along until you see the problem.  This isn't
really Cygwin-specific advise though.  You may want to read up on some
of the capabilities of 'gdb' to gain more insights into it's capabilities.
That should help you understand the things it can do to help you find
problems.

-- 
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/