Skip to content
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

rbx register instead of rbp - Applications will read the wrong memory block instead of the parameter value. #117

Open
bryancall opened this issue Feb 11, 2022 · 1 comment

Comments

@bryancall
Copy link

bryancall commented Feb 11, 2022

I ran this program over our API across versions and I am seeing these error show up for a few or our APIs. Here is a link to the report:
https://trafficserver.apache.org/compat_reports/traffic_server/9.0.x_to_9.1.x/compat_report.html#Symbol_Binary_Problems_High

I was able to git rid of the rpb errors by compiling our binary with -fno-omit-frame-pointer, but I was still seeing issues about the rbx register. Our API C code is statically linked into the server's binary to give some context.

Is this really an issue, sounds like it is, and if so is there a way I could fix this problem?

@bryancall
Copy link
Author

Changing the API C code to be included into a .so I am seeing the error change from:
The parameter mutexp became passed in rbx register instead of rbp.
to:
The parameter mutexp became passed in rbx register instead of r12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant