BitBanger
February 14th, 2003, 14:01
Hello,
I encountered the following problem when using bpx type breakpoints in SoftIce. When setting this kind of breakpoint in some applications program generates exception (execution of int 3 instruction) and is terminated when program flow reaches the address of bpx. Then when i remove bpx in SI by bc command and run the program again, the int 03 instruction is still at address of previous breakpoint even after I removed it in SI and stays there until i reboot the system (i did not yet discovered how to remove this int 03 instruction without reboot). My question is: Is this behaviour caused by the protection of the application which detects breakpoints and "patches" the program or is it problem of some other kind?
Thank you for your help.
BitBanger
I encountered the following problem when using bpx type breakpoints in SoftIce. When setting this kind of breakpoint in some applications program generates exception (execution of int 3 instruction) and is terminated when program flow reaches the address of bpx. Then when i remove bpx in SI by bc command and run the program again, the int 03 instruction is still at address of previous breakpoint even after I removed it in SI and stays there until i reboot the system (i did not yet discovered how to remove this int 03 instruction without reboot). My question is: Is this behaviour caused by the protection of the application which detects breakpoints and "patches" the program or is it problem of some other kind?
Thank you for your help.
BitBanger