Timeline for Window application - Does the debugger stop the window thread?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2017 at 9:58 | vote | accept | Duke Nukem | ||
| Jun 30, 2017 at 22:53 | comment | added | josh poley | @DukeNukem - edited my answer to provide more details / clarification. | |
| Jun 30, 2017 at 22:51 | history | edited | josh poley | CC BY-SA 3.0 |
Address comment request for clarification / details.
|
| Jun 30, 2017 at 22:31 | comment | added | Duke Nukem | Two solutions are exposed here: 1) blabb comment saying that the debugger does not do anything and it is simply waiting for an event to occur it doesn't know what the exe is doing. It may explain why we can't see the EIP changing. 2) the GUI can't be refreshed as threads are so fast. Which one is correct? | |
| Jun 30, 2017 at 22:16 | vote | accept | Duke Nukem | ||
| Jun 30, 2017 at 22:33 | |||||
| Jun 29, 2017 at 22:28 | comment | added | mrexodia | This is the correct answer. When the debuggee is running it makes no sense to query thread states constantly. If you are really interested you can double click the thread you're interested in and use the "Goto -> Origin" option to force refresh the registers and navigate to the current EIP/RIP. | |
| Jun 29, 2017 at 15:37 | history | answered | josh poley | CC BY-SA 3.0 |