Skip to content

Deadlock / application unresponsive when analyzing a specific Rust binary #7987

@amyspark

Description

@amyspark

Version and Platform (required):

  • Binary Ninja Version: 5.3.8876-dev Personal, bed91080
  • OS: windows
  • OS Version: 10
  • CPU Architecture: x86_64

Bug Description:

I'm building a new Rust plugin, and been using Binary Ninja to look inside the binary and determine feature footprint.

However, when I changed one specific feature, the binary produced by rustc caused Binary Ninja to stop responding.

Steps To Reproduce:

Load each of the files attached. The "good" version will never lock the app and finalize analysis in ~5 minutes. The "bad" version will cause the app to stop responding soon into "Phase 1: Analyzing" at around 3k entries.

Expected Behavior:

Both DLLs should load without a problem.

Screenshots:

N/A

Binary:

gstimagers.good.zip
gstimagers.bad.zip

Additional Information:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions