3139fc9767
When the debugger is run in sync mode, you need to be able to tell whether a hijacked resume is for some special purpose (like waiting for the SIGSTOP on attach) or just to perform a synchronous resume. Target::Launch was doing that wrong, and that caused stop-hooks on process launch in source files to behave incorrectly. <rdar://problem/48115661> Differential Revision: https://reviews.llvm.org/D58727 llvm-svn: 355213
6 lines
288 B
Plaintext
6 lines
288 B
Plaintext
break set -f stop-hook-threads.cpp -p "Break here to set up the stop hook"
|
|
break set -f stop-hook-threads.cpp -p "Break here to test that the stop-hook"
|
|
run
|
|
target stop-hook add -x 2 -o "expr lldb_val += 1" -o "thread list"
|
|
target stop-hook add -G true -o "script print('Hit stop hook')
|