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
- RE: [PATCH] Re: pthread Robert Collins
- RE: [PATCH] Re: pthread Suhaib Siddiqi
- RE: [PATCH] Re: pthread Robert Collins
- RE: [PATCH] Re: pthread Suhaib Siddiqi
- RE: [PATCH] Re: pthread Suhaib Siddiqi
- Re: [PATCH] Re: pthread Robert Collins
- RE: [PATCH] Re: pthread Suhaib Siddiqi
- Re: [PATCH] Re: pthread Robert Collins
- RE: [PATCH] Re: pthread Suhaib Siddiqi
- Re: [PATCH] Re: pthread Robert Collins
- Re: [PATCH] Re: pthread Harold Hunt
- Re: [PATCH] Re: pthread Robert Collins
- RE: [PATCH] Re: pthread Suhaib Siddiqi
- Re: [PATCH] Re: pthread Robert Collins
- Re: [PATCH] Re: pthread Alan Hourihane
- Re: [PATCH] Re: pthread Robert Collins
- Re: [PATCH] Re: pthread Alan Hourihane
- Re: [PATCH] Re: pthread Christopher Faylor
- Re: [PATCH] Re: pthread Robert Collins
- Re: [PATCH] Re: pthread Christopher Faylor
- Re: [PATCH] Re: pthread Alan Hourihane