François-Xavier Bourlet
François-Xavier Bourlet
Also, just to clear things up: libunwind != unwind API. backward uses the unwind API from gcc/clang. libunwind is an advanced library for walking the stack (with way more features...
Nice work. I saw your PR. And is the copy paste is mostly renaming. We can probably add some macro to represent the common parts. I don't have much time...
It works because in real life, most signals are not around failures of the memory allocator (ie: malloc) itself. As long as you can allocate memory, you are pretty ok....
Linux on arm 64bit should work fine. I haven't tried it though.
The more memory we allocate, the more likely something bad can happen if you are expecting a stacktrace on some cpu exception...
There is already completely featured libraries for this. Take a look at this one: https://chromium.googlesource.com/breakpad/breakpad I think this is close to what you want. In contrast backward-cpp is to be...
Sadly, the libraries used behind are using malloc like its free ;) So we cannot easily workaround that unless we write a zero allocation dwarf decoder... or patch the libraries....
See my inline comments. I really want to keep the library simplistic to add to an existing project, your changes are impending that, but it looks like it might possible...
sorry for the delay in responding. You might need to rebase/merge from master. See my comment and if you can make it work that would be great!
Yes, but we really want REG_RIP to be defined. The error address is architecture specific. Perhaps you can find a way to extract the error address from the context with...