google / google/sanitizers

Show stacks for unpoison & poison

Open
#191 17 comments 3 reactions 0 assignees View on GitHub
Priority-Medium ProjectAddressSanitizer Status-New Type-Enhancement
Dominant language
C
Stars
12.5k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

Originally reported on Google Code with ID 191

```
For normal malloc/free memory, a use-after-free results in the stack for the allocation,
the deallocation, and the final use.

For arena memory, a use-after-poison would ideally have the stack for the most recent
unpoison, the poison, and the final use. In addition to the allocation for the arena
itself, I guess.
```

Reported by `jruderman` on 2013-06-04 19:55:33

Contributor guide

Open the contributing guide

Research direction

The issue names no source files, tests, or entry points. Start by locating the arena poison and unpoison reporting paths and their existing stack-capture behavior; done means a use-after-poison report includes the most recent unpoison, poison, final-use, and arena-allocation stacks.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
devtools, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.