Home/ Questions/Q 8154111
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T16:14:03+00:00

Rather bizarrely the hpux unwind API _UNW_STACK_TRACE doesn’t take a file descriptor, but instead

  • 0

Rather bizarrely the hpux unwind API _UNW_STACK_TRACE doesn’t take a file descriptor, but instead takes a FILE*. The newer API uwx_stack_trace also takes a FILE*.

With both of these using buffered IO and not (signal safe IO interfaces) open/write/close, neither of these can safely be used in a signal handler (one of the most obvious places where one would wish to do so).

On one of our (probably now dead) ia64 platforms, we once had our own unwind implementation, but it was a beast to maintain and flaky, so I don’t want to go down that route again. Are there any other options for HPUX stack unwind?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I found the hpux documentation that details their stackwalk iterator interfaces. Unfortunately, and somewhat unbelievably, trying this out in the debugger shows that it’s busted in a signal context too (uwx_init calls malloc!)

    • 0