On Sat, 27 Apr 2002, Ronald Fenner wrote:
> if you get a core dump when it happens look at it and you'll find what
> function it was stuck in usually.
If you happen to catch the infinite loop in action, either attach gdb to
the running process
$ gdb <executable> <pid>
or cause a coredump
$ kill -SEGV <pid>
to look at the post-mortem. The former will provide you with greater
capabilities that might aid in debugging (e.g., you can call functions),
but, in a pinch, the latter should suffice.
I won't go into much more than that. One could write volumes on the zen
of UNIX and the craft of debugging, but it's not appropriate, here. Know
your tools.
-dak
--
+---------------------------------------------------------------+
| FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
| Archives: http://post.queensu.ca/listserv/wwwarch/circle.html |
| Newbie List: http://groups.yahoo.com/group/circle-newbies/ |
+---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 06/25/03 PDT