* Bart Smaalders <bart.smaalders at Sun.COM> [2007-03-09 20:53]: > > Some time ago (Solaris 9 development) I put walkcontext() > and printstack() into Solaris. Linux introduced backtrace() > at some point; there are now programs that will use either > one (dovecot, for example), but there are others that confine > themselves to backtrace() only. > > It's fairly simple to support for backtrace, backtrace_symbols, > and backtrace_symbols_fd for Solaris using the existing > walkcontext and support code for printstack(). Is this worth > doing?
Since we added err() and warn() (or at least were discussing it), it sounds okay--if it doesn't constrain anything you were thinking of doing in this space. (I also wonder if we need some counterpart of __EXTENSIONS__, which, if active, would hide the non-preferred API. Like #ifndef SUNOS_PREFERRED_API /* compatibility API */ #endif or something fancier. It may be too late for this sort of thing, of course.) - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems stephen.hahn at sun.com http://blogs.sun.com/sch/
