> Description : debug a running process for memoy leaks without > recompiling or restarting
Typo: "memory", not "memoy". > Memleax debugs a program for memory leaks by attaching to a running process, > similarly to how gdb's does. It then hooks into the target process's > invocation of memory allocation and free, and reports in real time the > memory blocks that it identifies as memory leaks. This section doesn't could be rewritten for clarity, the "'s" are wrong either way. > The default expiration threshold is 10 seconds; however, you should > always set this with the -e option according to your scenarios. This doesn't need to be in the package description. > It is very convenient to use, and is suitable for production > environments. Sounds like a nice tool indeed, thanks for packaging it :) > and then kill memleax (e.g. sent it a SIGINT with Ctrl-C) to stop > monitoring. "sent" -> "send". But again this probably doesn't need to be in the description. > Differences from Valgrind: > . > * Valgrind starts the target process, while memleax attaches to on that is > already running. Nor this. Steve -- https://www.steve.org.uk/
