You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#306 added frame pointers so that backtraces would be available from failed stack probes. Unfortunately, this does not work in build configurations which use DWARF/CFI information for unwinding. (On Fuchsia we use this exclusively, but it's an option on other platforms as well.)
The way of enabling backtraces on these platforms is to use CFI directives, like #305 did. Unfortunately, that implementation was messier due to needing external assembly files. Still, it's the only way to get full backtrace information in DWARF.
The text was updated successfully, but these errors were encountered:
I'm not familiar with it myself, but if LLVM inline assembly has a way to support this that'd be the best way to go. If not, though, using assembly files for rust-lang/rust builds and having the inline-Rust used for other builds seems like a possible way to go to fix this
#306 added frame pointers so that backtraces would be available from failed stack probes. Unfortunately, this does not work in build configurations which use DWARF/CFI information for unwinding. (On Fuchsia we use this exclusively, but it's an option on other platforms as well.)
The way of enabling backtraces on these platforms is to use CFI directives, like #305 did. Unfortunately, that implementation was messier due to needing external assembly files. Still, it's the only way to get full backtrace information in DWARF.
The text was updated successfully, but these errors were encountered: