I'm trying to debug an application that uses QT GUI library. The problem is that I can't even start debugging as ollydbg seems to be processing ~1k events per second where in stack trace I see all of them running inside QT. The application has very fancy GUI (blending, custom window and buttons etc) and perhaps that is what hangs the debugger as it tries to process all this. Eventually it bluescreens. Can I somehow force olly to skip or ignore these events?

  • It bluescreens?? Could you post the crashdump? Mar 8 '14 at 14:32
  • It's weird. I tried to open memory.dmp in BlueScreenView (freeware) and it shows nothing. No raw data, no drivers. Just basic information like termination string (CRITICAL_OBJECT_TERMINATION) bug check code and size. Is it possible that dumps are corrupted?
    – Mike
    Mar 8 '14 at 19:27
  • WinDbg is the preferred way to review a crashdump. Mar 8 '14 at 22:15
  • Alright. If the application happens to crash the system, it might use some rootkit to prevent memory analysis and whatnot. Anyway, I tried with different QT application and result is the same (yet, perhaps it's not QT fault but coincidence). 100-400 events per second and I can't use the application since it's "stuck" (I can't even maximize it or open popup menu -- when right clicking the icon on task bar).
    – Mike
    Mar 13 '14 at 11:05
  • Perhaps some extensive applications really do process lot of events, even in the background. How can I debug such applications? This is what the stack trace shows (it hits new events all the time, very quickly) cap.ring0.cc/c7234a2d45e076d62aecf28a74e95c29.png
    – Mike
    Mar 13 '14 at 11:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.