You may be looking for ‘showallstacks’.

I'm familiar with that, but (from memory, it's been a few months) if you switched to a particular thread the backtrace command was, in general, a lot more complete.

Function arguments can’t always be recovered; if there is no symbol information the debugger cannot know the arguments that were passed to the function, or if the function has been optimised or simply generated in certain ways the argument values may no longer exist anywhere by the time a call is made to the next frame down your stack.

No argument there; booting with a debug kernel certainly made the backtrace more useful. --Ken _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com