xusheng

I have updated the issue title. This issue will likely be resolved soon. We have decided against the originally planned approach. Instead, we are not adding an overlay to the...

There is a current workaround and a future solution to this. When you launch the target, set `Input File` to an empty string, so that the debugger will NOT try...

Could you try rebasing your binary and see how long it takes? The copying process is essentially the same as a rebasing, though with the same base.

Now that you said the ASLR is disabled, I think it is taking a bit too long. Could you please via with the binary via slack or email?

> By the way, I'm just now realizing that my wording was misleading: The copying takes a couple of minutes, but it's the full reanalysis that happens in the debugger...

This should have been fixed since we are no longer creating a debugger binary view during launch. The original view (e.g., PE view), is used for debugging and the extra...

This is similar to https://github.com/Vector35/debugger/issues/567, but it is different. Because in https://github.com/Vector35/debugger/issues/567, it does not even get to the point where `OpenDumpFile` is called. Also relevant: https://github.com/Vector35/debugger/issues/573

Duplicate of: https://github.com/Vector35/debugger/issues/83. This issues has been around for a file since it requires some changes on BN to be able to programmatically highlight the edge

@plafosse I am unable to reproduce this, could you please record a video for it?

The key to a repro for this is to set `debugger.stopAtEntryPoint` to false, so that when the target is launched, it runs freely on its own