Coming up with canonical mdb(1) use is a little like decscribing the
canonical bug -- it doesn't really make sense since each problem is a
little different. The best examples might be just on ordinary bugs; you
can find some here:
http://blogs.sun.com/roller/page/mws?entry=sendmail_died_in_a_two
http://blogs.sun.com/roller/page/jwadams?entry=brokenness_hides_itself
Here's Eric Schrock's GDB to MDB migration guide:
http://blogs.sun.com/roller/page/eschrock?entry=gdb_to_mdb
http://blogs.sun.com/roller/page/eschrock?entry=gdb_to_mdb_migration_part
Jonathan Adams's MDB background and cheat sheet:
http://blogs.sun.com/roller/page/jwadams?entry=an_mdb_1_cheat_sheet
> - libumem/mdb example about how to discover a memory leak or a corrupted
> heap for: evolution, firefox, staroffice
Here are some libumem-related blog posts:
http://blogs.sun.com/roller/page/ahl?entry=solaris_10_top_11_20
http://blogs.sun.com/roller/page/jwadams?entry=the_implementation_of_findleaks
Adam
--
Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl
