Hang when killing target process that causes Access Violations on macOS

Open
#338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, macos
Domain
devtools, operating-systems, reverse-engineering

Research direction

Reproduce on macOS 12.6 with an M1 and the listed Binary Ninja versions, using a target that raises an Access Violation while a function is stepped over. Start by tracing the debugger's step-over and kill-process behavior; done means the exception does not loop indefinitely and killing the target does not hang Binary Ninja.

Written by the indexing model from the issue text.

Description

bug hang Impact: High LLDB Adapter

macOS 12.6, M1, Binary Ninja 3.2.3814 (verified against dev 98d54871 as well)

If the process being debugged causes an Access Violation in a function that is being stepped over, the debugger will seemingly get stuck in a loop, as the Access Violation repeatedly and rapidly appears in the status bar and the debugger buttons rapidly switch states. Clicking the kill process button causes Binary Ninja to hang with spinning a rainbow.

(See internal slack for stack trace.)

Dominant language
C++
Stars
331
Forks
33
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/debugger

All issues in Vector35/debugger

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.