Skip to content
This repository has been archived by the owner on Jun 28, 2022. It is now read-only.

Bounds_checker memory corruption issue #6

Open
kumarak opened this issue Jul 26, 2013 · 0 comments
Open

Bounds_checker memory corruption issue #6

kumarak opened this issue Jul 26, 2013 · 0 comments
Assignees
@kumarak
Labels
bug

Comments

@kumarak
Copy link
Contributor

kumarak commented Jul 26, 2013

How to Reproduce:

  1. Set client as bounds_checker
  2. Run iozone test in throughput mode with direct i/o enabled. Run with two reader/writer thread.
  3. Page fault at bound_policy::visit_reader(...), memory corruption

Related:

Memory corruption is happening because it is trying to instrument a corrupted instruction. it shows size_index more than 5.

The issue is temporarily fixed by not instrumenting the instruction when size_index is more than 5
@ghost ghost assigned kumarak Jul 26, 2013
kumarak added a commit that referenced this issue Jul 26, 2013
@kumarak
Issue #6 logged for the bounds checker and temporarily fixed by not i…
7e1ea9b 
…nstrumenting the instruction if watchpoint_tracker value is corrupted;
@renzhengeek renzhengeek mentioned this issue Mar 3, 2014
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@kumarak kumarak

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kumarak