Feature request: have FpDebug ignore some int 3 instructions

Summary

When running 32 bit code, FpDebug is activated by int 3 instructions that occur in the Windows loader. This is very inconvenient.

System Information

It is a verified problem in Windows 7 and likely in other versions of Windows. The problem does not occur with 64 bit programs only 32 bit ones.

Example Project

Load a 32 bit "hello world" program. The loader will break somewhere in ntdll.dll.

Since it is very convenient that FpDebug honors int 3, it would be nice if it would make a distinction between int 3s it is willing to honor and those it is not. One possibility is to look at the instruction that follows the int 3, in the case of DebugBreak() (which FpDebug does and should honor) it must be followed by a "ret" instruction. Making the "ret" a condition for honoring the int 3 would weed out most, if not all, unwanted int 3s. Of course, any other method that works is perfectly fine too.

Thank you for your consideration to this request.