summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities/command_source/my.py
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2019-03-01 18:13:38 +0000
committerJim Ingham <jingham@apple.com>2019-03-01 18:13:38 +0000
commit3139fc976795c1cb29c46b4c5cb7c571e619a73c (patch)
treecef747669300658cba860bea52640587bb13c455 /lldb/packages/Python/lldbsuite/test/functionalities/command_source/my.py
parent21f7c35df1de6c2b16aa663e26cb4d09099118a2 (diff)
downloadbcm5719-llvm-3139fc976795c1cb29c46b4c5cb7c571e619a73c.tar.gz
bcm5719-llvm-3139fc976795c1cb29c46b4c5cb7c571e619a73c.zip
Resubmit r354706 with a fix for process launch.
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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/command_source/my.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud