[llvm-bugs] [Bug 43918] New: Debugserver doesn't continue with specified signal in `vCont` packet

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=43918

            Bug ID: 43918
           Summary: Debugserver doesn't continue with specified signal in
                    `vCont` packet
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev at lists.llvm.org
          Reporter: dmitry.neverov at gmail.com
                CC: jdevlieghere at apple.com, llvm-bugs at lists.llvm.org

Created attachment 22778
  --> https://bugs.llvm.org/attachment.cgi?id=22778&action=edit
delve.log

I'm debugging the following go program on MacOS 10.14.6.

    package main

    import (
      "fmt"
      "os"
      "os/signal"
    )

    func main() {
      sigs := make(chan os.Signal, 1)
      signal.Notify(sigs, os.Interrupt)
      sig := <- sigs
      fmt.Printf("Got a signal '%v', start shutting down...\n", sig)
    }


The program waits for the SIGINT and exits. I'm sending SIGINT via `kill -2
<pid>`. Attached logs show that debugserver notifies go debugger that the
program got SIGINT (`$T02` package), go debugger responds with `vCont;C02`,
debugserver receives the packet, but doesn't call `MachProcess::Signal` and the
program doesn't get the SIGINT.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191106/cbd77c5d/attachment.html>