site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hello, Thanks, Jonas _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Is there a standard way to crawl the stack safely when you are in a procedure called by signal handler? Just following the saved stack pointers causes a crash when you arrive at the signal frame. Inside the signal handler itself it's of course possible to obtain the original stack pointer from the signal's context, but when you're inside a function called from a signal handler, this function may not know there's a signal frame somewhere higher up on the stack. I looked at the gdb code, but that one simply tries to peek at some values and catches any SIGSEGVS that may occur as a result. Is this really the only way? Or is there a default implementation in one of the system libraries which I can use? (I don't need symbolic resolution, just the addresses themselves). This email sent to site_archiver@lists.apple.com