Thanks for your advice, I will order this book you recommended. I just learned mdb and Dtrace recently. I feel that mdb is good for core dump analysis and dtrace for permance tunning. But in the early stage of development, especially when code is not stable, it is better to be able to step in/over any subroutine and examine local and global flags value. Dtrace seems only display subroutine entry and exit value, but unable to display how a local flag's value changes during the progress, neither can it set a break point to stop and let us check value of other local/global flags when something bad happens. Anyone who is used to using VC++ or Gdb will feel very inconvenient.
Solaris may have special reasons not to provide a source level debugger, however, since Linux and Windows all provide for the driver development, it is quite natural to expect Solaris develop a similar tool. I will order the book you recommended and hopefully, I can understand the advantage and great usefulness of mdb and DTrace. Thanks! Tom This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
