This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [PATCH] Re: pthread


Sure - as long as you get sensible stack data.

One of the nice things about printf bombing is that you don't need the
stack to be in good order to get some idea of where its dying.

Alternatives include:
dumper.exe to get a core dump
dynmically launch gdb
breakpoints.

on the minus side.
multi thread apps can be nightmares to debug. Debugging often removes
race appearances.

Rob

----- Original Message -----
From: "Harold Hunt" <huntharo@msu.edu>
To: "Cygx (E-mail)" <cygwin-xfree@sources.redhat.com>
Sent: Friday, April 20, 2001 12:42 AM
Subject: RE: [PATCH] Re: pthread


> Why not use gdb to set breakpoints and step through the code?  That's
what
> Pierre Humblet and I did to find the crashing and freezing bugs.
>
> First launch gdb with the graphical environment:
> gdb XWin
>
> Within gdb, open the console (Ctrl+N):
> break Function1
> break Function2
> run -screen 0 640x480x16 -from foo.host.org -query bar.host.org
>
> Start stepping with (S) or nexting with (N) when you reach a
breakpoint.
> From there you only have about two weeks until you'll find the bug :)
>
> Okay okay, you guys probably already knew how to do this, but I felt
like
> writing it down somewhere for my own and other's reference :)
>
> Harold
>
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]