Killing or detaching debugger after step-into on unresolved (sub_) function jumps binary view to end of binary

[Weitao-Sun]

Version and Platform (required):

• Binary Ninja Version: 6.1.10552
• OS: Ubuntu Linux
• OS Version: 26.04
• CPU Architecture: x64 (x86_64)
• Local or Remote Debugging: Local

Bug Description:
When using the debugger's "step into" on an unresolved function (one displayed as sub_...), then killing or detaching the debugger, the binary view unexpectedly jumps to the end of the binary instead of remaining at a sensible location.

Steps To Reproduce:

1. Open a binary in Binary Ninja and start a local debug session
2. Step into a call to an unresolved function (displayed as sub_...)
3. Kill or detach the debugger
4. Observe that the binary view jumps to the end of the binary

Expected Behavior:
Killing or detaching the debugger after stepping into an unresolved function should not cause the binary view to jump to the end of the binary.

Screenshots/Video Recording:

Screencast.From.2026-08-31.12-37-45.webm

[UvuvDev]

When inside of a library function, this is intended behavior. In the video shown printf is being stepped into so you are in LibC. Test with a stripped binary that does not have symbols, outside of a loaded library.