Timeline for Can I set more than 4 memory access breakpoints in WinDbg?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 25, 2018 at 20:23 | answer | added | NirIzr | timeline score: 1 | |
| Jun 24, 2018 at 17:14 | vote | accept | c00000fd | ||
| Jun 23, 2018 at 19:25 | comment | added | c00000fd |
@Megabeets: I'm not sure if I'm using that bp correctly. Say, I have a DWORD in memory that I want to track. I call bp 03DBF450. I then do bl and receive 1 e 03dbf450 0001 (0001) 0:**** but then if I run the debuggee I get an exception from IDA pro: 779A2228: The instruction at 0x779A2228 referenced memory at 0x14. The memory could not be written -> 00000014 (exc.code c0000005, tid 5928) and the debuggee crashes. This doesn't happen if I don't use bp command.
|
|
| Jun 23, 2018 at 11:18 | comment | added | Megabeets |
ba is a processor breakpoint (hardware breakpoints). use bp instead. For more breakpoints in radare2, read here.
|
|
| Jun 23, 2018 at 10:30 | answer | added | Paweł Łukasik | timeline score: 5 | |
| Jun 23, 2018 at 8:16 | history | asked | c00000fd | CC BY-SA 4.0 |