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.

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

Freeze when setting many breakpoints #1954

Open
mrexodia opened this Issue May 31, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@mrexodia
Member

mrexodia commented May 31, 2018

basically attach to any process, let it run, go to symbols, kernel32.dll, sort by type, select all exports, press F2

From ProN00b

@JayFoxRox

This comment has been minimized.

JayFoxRox commented Jun 5, 2018

I've never used x64dbg, but this issue description does not seem to be about what the title suggests.

It could easily be an issue with the order of breakpoint creation and the debugger setting a breakpoint on a function it still has to call itself, or a function which is invoked somewhere during breakpoint handling.

While x64dbg probably shouldn't freeze, this doesn't sound like an issue with ~"too many breakpoints" but ~"some bug with the breakpoint related code (handling or installation)".

@mrexodia

This comment has been minimized.

Member

mrexodia commented Jun 5, 2018

I have used x64dbg before and setting a breakpoint is done like this:

  • cheap checks for housekeeping
  • call TitanEngine to set the breakpoint (write process memory + some other stuff)
  • add breakpoint in x64dbg’s housekeeping
  • gui refresh

Now when setting 100 breakpoints from inside the gui you get 100 refresh signals and a lot of memory reads that pretty quickly flood the message queue causing a massive freeze.

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