11accd4d71
Instead of unconditionally returning all present goroutines, GoroutinesInfo now allows specifying a range (start and count). In addition to the array of goroutines and the error, it now also returns the next goroutine to be processed, to be used as 'start' argument on the next call, or 0 if all present goroutines have already been processed. This way clients can avoid eating large amounts of RAM while debugging core dumps and processes with a exceptionally high amount of goroutines. Fixes #1403 |
||
|---|---|---|
| .. | ||
| api | ||
| debugger | ||
| rpc1 | ||
| rpc2 | ||
| rpccommon | ||
| test | ||
| client.go | ||
| config.go | ||
| listenerpipe.go | ||
| rpccallback.go | ||
| server.go | ||