10 Sep
2009
10 Sep
'09
5:35 a.m.
On Wed, Sep 09, 2009 at 07:15:13PM +0200, Bernhard Duebi wrote:
thank you for having a look at my problem. Any idea how I can find out what library is doing it and how it is triggered ?
compile your program with debug symbols (-g) and attach to it with the debugger (dbx -p <pid>) once it enters the loop. Then examine the stack back-trace and see where it's stuck and how it got there.