thank you. i see that there are also .crash file generated at ~/Library/Logs/DiagnosticReports ``` ➜ ~ ls Library/Logs/DiagnosticReports/a.out_2020-10-02-1337* -lh -rw------- 1 zah _analyticsusers 22K Oct 2 13:37 Library/Logs/DiagnosticReports/a.out_2020-10-02-133721_hac.crash -rw------- 1 zah _analyticsusers 21K Oct 2 13:37 Library/Logs/DiagnosticReports/a.out_2020-10-02-133751_hac.crash ``` could go generates .crash file? On Saturday, October 3, 2020 at 3:26:13 AM UTC+8 Ian Lance Taylor wrote:
> On Thu, Oct 1, 2020 at 10:44 PM aihui zhu <mr.z...@gmail.com> wrote: > > > > C program could generate a core dump file, my os is Big Sur beta. > > Thanks. > > I see now that for darwin-amd64 we do not generate core dumps. Sorry > for forgetting about that. > > We have this comment: > > // OS X core dumps are linear dumps of the mapped memory, > // from the first virtual byte to the last, with zeros in the gaps. > // Because of the way we arrange the address space on 64-bit systems, > // this means the OS X core file will be >128 GB and even on a zippy > // workstation can take OS X well over an hour to write (uninterruptible). > // Save users from making that mistake. > > It may be worth investigating whether this is still a problem on > current macOS systems. The comment in question is in > runtime/signal_unix.go. > > Ian > -- 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/b6a77509-a810-4d1f-bf50-6dc3e1fc94d0n%40googlegroups.com.
