[ILUG] [OT] Looking for recommendations for solaris memory checker

[Paul Jakma]

On Wed, 4 May 2005, Justin Mason wrote:

> ooh good tip!
>
> FWIW -- Sean, if purify is the featureset you're after, which it sounds
> like from that list you posted, then go use valgrind.  It's
> indistinguishable (saying this as someone who's spent a lot of time with
> purify).

IIRC, valgrind is i386 specific, which might not help Sean if he's 
running Solaris on UltraSPARC...

Whatever, if you have Solaris 9 or 10, then libumem is (IMHO) better, 
if you want to hunt down leaks or double-frees. It doesn't try to 
'emulate' i386 so its /far/ less heavy on run-time.

You can also do things like take a coredump (gcore) and run dbx/mdb 
on /that/ (useful for when you cant replicate the leak, but your 
customer can ;) - just ask them to set the relevant libumem 
environment variable and then 'gcore' the process once the leak is 
established and send you the core.)

mdb is really good, but a bit cryptic and alien initially if you're 
used to gdb though.

regards,
-- 
Paul Jakma	paul at clubi.ie	paul at jakma.org	Key ID: 64A2FF6A
Fortune:
No wonder you're tired!  You understood so much today.