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.

Sign up for GitHub

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

Jump to bottom

Stack Exhaustion/Crash in OutlineResolver for Pathological Case #4437

Closed
bpotchik opened this issue Jun 24, 2023 · 1 comment
Closed

Stack Exhaustion/Crash in OutlineResolver for Pathological Case #4437

bpotchik opened this issue Jun 24, 2023 · 1 comment
Assignees
@bpotchik
Labels
Effort: Low Issue should take < 1 week Impact: Medium Issue is impactful with a bad, or no, workaround Type: Crash Issue is a crash or deadlock
Milestone
Coruscant

Comments

@bpotchik
Copy link
Member

  • Repro Steps
  1. Using the available binary, create a thumb function at e2099fb2
  2. Witness crash

Anyone from V35 should search for "that guy's crashing firmware (private binary)"
@bpotchik bpotchik added Type: Crash Issue is a crash or deadlock Effort: Low Issue should take < 1 week Impact: Medium Issue is impactful with a bad, or no, workaround labels Jun 24, 2023
@bpotchik bpotchik added this to the Coruscant milestone Jun 24, 2023
@bpotchik bpotchik self-assigned this Jun 24, 2023
@bpotchik
Copy link
Member Author

Fixed in 3.5.4357-dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bpotchik bpotchik

Labels
Effort: Low Issue should take < 1 week Impact: Medium Issue is impactful with a bad, or no, workaround Type: Crash Issue is a crash or deadlock
Projects
None yet
Milestone
Coruscant
Development

No branches or pull requests
1 participant
@bpotchik