Message147656
| Author |
neologix |
| Recipients |
Trundle, ncoghlan, neologix, pitrou, tim.peters |
| Date |
2011年11月15日.08:11:38 |
| SpamBayes Score |
5.4883485e-06 |
| Marked as misclassified |
No |
| Message-id |
<1321344699.51.0.923120188191.issue13390@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Together with -R, it can help chase those memory leaks which aren't
> reference leaks (see c6dafa2e2594).
Valgrind does a much better job at this: it will also show you where the leaked blocks were allocated.
OTOH, Valgrind is Linux-only and slow, but since I haven't used the '-R' option much, I don't know how usable this will be in practice (detecting memory leaks is one thing, identifying them is even better :-). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年11月15日 08:11:39 | neologix | set | recipients:
+ neologix, tim.peters, ncoghlan, pitrou, Trundle |
| 2011年11月15日 08:11:39 | neologix | set | messageid: <1321344699.51.0.923120188191.issue13390@psf.upfronthosting.co.za> |
| 2011年11月15日 08:11:38 | neologix | link | issue13390 messages |
| 2011年11月15日 08:11:38 | neologix | create |
|