gimli-rs/gimli

evaluator doesn't pass max_iterations when computing the frame base

Open

#166 opened on Dec 13, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (130 forks)github user discovery
bugeasyhelp wanted

Repository metrics

Stars
 (990 stars)
PR merge metrics
 (PR metrics pending)

Description

If the caller sets the maximum number of iterations to allow, then when computing the frame base, this value should be passed in. Otherwise it seems that it might be possible to use this to circumvent the limiting step.

Contributor guide

Research direction
Inspect the evaluator code in gimli to ensure max iterations is passed when computing the frame base.
Tech stack
rust
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70