mossberg added a comment.

I wanted to also mention that this patch won't address buggy behavior if, for 
example, the stub takes a function pointer on the stack (vs a normal data 
pointer). In this case, the executable check will succeed, and the breakpoint 
will be written, but to a potentially arbitrary code address. This may or may 
not lead to the debugger "randomly" breaking out later in a debug session if or 
when that code happens to be executed (I've reproduced this, but also seen some 
very confusing behavior where in some situations the breakpoint logging will 
say a breakpoint is written, but it doesn't seem like this was actually the 
case.)


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D71372/new/

https://reviews.llvm.org/D71372



_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to