Feature request: allow running setup commands after loading executable

Type: Debugger

Describe the bug

• OS and Version: macOS 10.12.6
• VS Code Version: 1.27.2
• C/C++ Extension Version: 0.18.1
• Other extensions you installed (and if the issue persists after disabling them): Auto Comment Blocks, Better TOML, Bookmarks, CodeLLDB, EditorConfig, Git Blame, Go, hexdump, Markdown TOC, Monokai Pro, Ruby, Ruby Solargraph, Rust (rls), SpellChecker

My application makes extensive use of POSIX signals to interrupt system calls (see siginterrupt()). I would like to have the debugger ignore these signals. In lldb this can be done with:

process handle -n false -p true -s false SIGUSR1

One caveat is that this must be run after the executable has been loaded by lldb, not before. But there seems to be no way to tell cpptools to automatically run the above for me after loading the executable. I've already tried setupCommands, but that only runs stuff before loading the executable.

To Reproduce
Please include a code sample and launch.json configuration.

{
    "name": "(lldb) Launch CxxTestMain",
    "type": "cppdbg",
    "request": "launch",
    "program": "${workspaceFolder}/buildout/test/cxx/main",
    "args": ["-g", "Core_ApplicationPool_PoolTest:3"],
    "stopAtEntry": true,
    "cwd": "${workspaceFolder}/test",
    "environment": [],
    "logging": {
        "moduleLoad": false,
        "trace": true,
        "traceResponse": true
    },
    "MIMode": "lldb",
    "osx": {
        "MIMode": "lldb",
        "setupCommands": [
            { "text": "settings set target.x86-disassembly-flavor intel" },
            { "text": "b malloc_error_break" },
            { "text": "b Passenger::breakpoint" },
            { "text": "process handle -n false -p true -s false SIGPIPE" },
            { "text": "process handle -n false -p true -s false SIGUSR1" }
        ]
    }
},

The process handle setupCommands have no effect: lldb still breaks on SIGPIPE and SIGUSR1.

Additional context
If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json

https://gist.github.com/FooBarWidget/c5e000a32ebf74e0b64972fc56067e45