5dcf5cc0e0
In the presence of OS plugins, StopInfoMachException currently
propagates breakpoint stop reasons even if those breakpoints were not
intended for a specific thread, effectively removing our ability to set
thread-specific breakpoints.
This was originally added in [1], but the motivation provided in the
comment does not seem strong enough to remove the ability to set
thread-specific breakpoints. The only way to break thread specific
breakpoints would be if a user set such a breakpoint and _then_ loaded
an OS plugin, a scenario which we would likely not want to support.
[1]:
ab745c2ad8 (diff-8ec6e41b1dffa7ac4b5841aae24d66442ef7ebc62c8618f89354d84594f91050R501)
10 lines
209 B
C
10 lines
209 B
C
#include <stdio.h>
|
|
|
|
int main (int argc, char const *argv[], char const *envp[])
|
|
{
|
|
puts("stop here"); // Set breakpoint here
|
|
puts("hello");
|
|
puts("Set tid-specific breakpoint here");
|
|
return 0;
|
|
}
|