On Fri, Oct 2, 2020 at 9:23 PM aihui zhu <mr.zh...@gmail.com> wrote: > I mean that is there any way to expose SIGSEGV to macOS system just like a > pure C program, so that the system could generate .crash file automatically. > currently, seems that go itself catch the SIGSEGV signal, and prints go > trace back, so it doesn't trigger system default behavior for SIGSEGV. >
That is correct. And, no, there is no way for that to result in a core dump unless you build a custom Go runtime that changes the behavior of the "crash()" function in src/runtime/signal_unix.go. That is for the reason explained in the doc string in that function: You would end up with a huge core dump file that would probably take an hour or more to create. Do you actually have enough disk space (> 128 GB free space) and are willing to wait upwards of an hour for the core file to be created? If so then I, and no doubt others, would be interested in hearing from you why letting Go behave that way on macOS is sensible for 99% of people running Go programs on macOS. -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CABx2%3DD9-qWpfrHzo6SHspAfxbk7EymGmSbj2Wb4squ1iRur-hg%40mail.gmail.com.
