3 Mar
2004
3 Mar
'04
10:08 a.m.
Petter Holmström wrote:
Dieter Maurer wrote:
Use "gdb" and attach to the main process. Use "info threads", "thread <threadno>" and "backtrace" to learn about the various threads, select a thread and show where it is lingering.
OK, I first made the server freeze with the benchmark program. I then ran gdb with the following command:
<snip> Problem solved (I think). I had two external methods that displayed the operating system's name and uptime in the colophon, and when I removed the calls to these the problem disapperaded. Now I can really torture the server with load without it hanging itself. Great! -Petter-