forked from External/ergo
developing: Add advice for debugging hangs
This commit is contained in:
parent
300d02bd9c
commit
479cd376d2
1 changed files with 9 additions and 0 deletions
|
|
@ -34,3 +34,12 @@ https://github.com/DanielOaks/irc-stress-test
|
|||
|
||||
As well, there's a decent set of 'tests' here, which I like to run Oragono through now and then:
|
||||
https://github.com/DanielOaks/irctest
|
||||
|
||||
|
||||
## Debugging Hangs
|
||||
|
||||
To debug a hang, the best thing to do is to get a stack trace. Go's nice, and you can do so by running this:
|
||||
|
||||
$ kill -ABRT <procid>
|
||||
|
||||
This will kill Oragono and print out a stack trace for you to take a look at.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue