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

Enable malloc/delete/new/free mismatch checks on Windows #309

Closed
ramosian-glider opened this issue Sep 1, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@ramosian-glider
Copy link
Member

commented Sep 1, 2015

Originally reported on Google Code with ID 309

This is a bug to track the progress of enabling malloc/delete/new/free mismatch checks
on Windows.

They were probably disabled because these mismatches are usually safe on Windows, so
there should be quite a few places in e.g. Chromium where these checks fire.

I think we currently don't have any way to control these checks on per-function basis,
it's either completely off or on.

Reported by timurrrr@google.com on 2014-05-12 14:01:04

@ramosian-glider

This comment has been minimized.

Copy link
Member Author

commented Sep 1, 2015

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

  • Labels added: ProjectAddressSanitizer
@ramosian-glider

This comment has been minimized.

Copy link
Member Author

commented Sep 1, 2015

Adding Project:AddressSanitizer as part of GitHub migration.

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

@rnk

This comment has been minimized.

Copy link
Contributor

commented Dec 3, 2015

Personally I expect this will be a huge pile of work. It is much more difficult to reliably interpose operator new / delete on Windows, and that's what's needed to implement this.

Given that this is really hard and nobody is working on it, we can close it for now.

@rnk rnk closed this Dec 3, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.