[Lldb-commits] [PATCH] D15834: Handle hardcoded breakpoints on Windows (e.g., int3 or __debugbreak())

[Pavel Labath via lldb-commits]

labath added a comment.

Hm.. it seems I have misunderstood the purpose of __builtin_trap and the respective test. The function seems to generate in illegal opcode (ud2) instead of the expected int3 breakpoint. And according to the original commit message, it seems the test was added to verify that this illegal instruction does not confuse lldb/llvm. After ud2/SIGILL, it is not possible (without additional tricks) to continue the app like your test does.

So it seems that these are two tests are not that related after all, and we might as well keep them separate. I am sorry for the extra work caused by this.


http://reviews.llvm.org/D15834