Navigation Menu

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

Jump to bottom

Revisit memcpy()/memmove() handling on OSX after we drop support for 10.8 #226

Closed
ramosian-glider opened this issue Aug 31, 2015 · 3 comments
Closed

Revisit memcpy()/memmove() handling on OSX after we drop support for 10.8 #226

ramosian-glider opened this issue Aug 31, 2015 · 3 comments
Labels
OpSys-OSX Priority-Medium ProjectAddressSanitizer Status-Accepted Type-Enhancement

Comments

@ramosian-glider
Copy link
Member

Originally reported on Google Code with ID 226

As of Clang r191081 both memcpy() and memmove() on Darwin are intercepted with a function
with memmove semantics, i.e. no overlap checks are performed.
Once it's possible to intercept memcpy() and memmove() separately, we may want to reinstate
the overlap checks in the memcpy interceptor.

Reported by ramosian.glider on 2013-09-20 11:01:26
@ramosian-glider
Copy link
Member Author

Reported by ramosian.glider on 2015-07-30 09:05:31

  • Labels added: ProjectAddressSanitizer

@ramosian-glider
Copy link
Member Author 

Adding Project:AddressSanitizer as part of GitHub migration.

Reported by ramosian.glider on 2015-07-30 09:06:55

@ramosian-glider
Copy link
Member Author

memcpy() and memmove() are actually the same function (memmove) on 10.8+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
OpSys-OSX Priority-Medium ProjectAddressSanitizer Status-Accepted Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ramosian-glider