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

[Windows] Reports on global OOB accesses are not well tested yet #49

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

Comments

@ramosian-glider
Copy link
Member

Originally reported on Google Code with ID 49

I have a local test with intentional global OOB.

A few weeks ago the bug was not detectable by ASan, but now it is (not clear how -
no action was taken).
I'll commit the test as soon as code.google.com stops failing on commit.

Also, I was not able to find the global OOB on SPEC CPU2006 464.h264ref
(see http://code.google.com/p/address-sanitizer/wiki/FoundBugs#Spec_CPU_2006 )

Reported by timurrrr on 2012-03-16 13:18:18

@ramosian-glider
Copy link
Member Author

Reported by konstantin.s.serebryany on 2012-03-16 16:40:42

@ramosian-glider
Copy link
Member Author

FTR, the global-OOB test referenced above was committed in r1242 and works fine on the
bot.

Reported by timurrrr on 2012-03-16 18:12:06

@ramosian-glider
Copy link
Member Author

Reported by timurrrr on 2012-03-16 18:45:17

  • Labels added: Component-Tests

@ramosian-glider
Copy link
Member Author

Reported by timurrrr@google.com on 2014-05-14 13:56:28

  • Status changed: Fixed

@ramosian-glider
Copy link
Member Author

Adding Project:AddressSanitizer as part of GitHub migration.

Reported by ramosian.glider on 2015-07-30 09:12:58

  • Labels added: ProjectAddressSanitizer

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

No branches or pull requests

1 participant