-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add_trace_back doesn't work correctly on 32-bit systems #47
Comments
Thanks. I have never tested on these platforms, I'd appreciate further insights. Does libbacktrace work there (it comes with its own test suite)? Same question for libunwind? Does the dependent procmaps R package pass the tests? |
I'm not sure about I just noticed that I didn't have The |
I debugged this a little by printing out stuff in
|
libbacktrace is pretty much self-contained at https://github.com/ianlancetaylor/libbacktrace. I think winch has an exact copy of an earlier state. AFAIR, to use libunwind you'd need to change the code so that What does |
Ah, I did not realize that the vendored copy of libbacktrace is complete; I ran Output from `Rscript -e 'procmaps::procmap_get(as_tibble=FALSE)'`
|
From your description it seems that IPs are retrieved incorrectly. The C code collects IPs, formats them as hex string and passes them on to the R code. I wonder if there's a chance to replicate this on Linux or perhaps even on GitHub Actions. |
On i686 and armv7hl, the tests in
test-add_trace_back.R
fail and seem to be missing some bits of the traceback. winch also outputs a warning oflibR not found in backtrace, can't merge.
The text was updated successfully, but these errors were encountered: