yes, there are only go stack trace, and no core file was generated. with a 
pure C program, it could generate core file in /cores directory.

On Friday, October 2, 2020 at 10:16:51 AM UTC+8 Ian Lance Taylor wrote:

> On Thu, Oct 1, 2020 at 5:39 PM aihui zhu <[email protected]> wrote:
> >
> > I have enabled coredump with `ulimit -c unlimited`, and run the binary 
> with GOTRACEBACK=crash, but it only outputs the go stack trace when crash.
>
> There are two different things. There is the stack trace emitted when
> a program crash. And there is the core dump file generated by the
> kernel when a program crashes (if GOTRACEBACK=crash is set). It is
> normal for the stack trace to only show Go functions (though you could
> try importing github.com/ianlancetaylor/cgosymbolizer). I'm not
> clear: are you saying that you see only the stack trace, and that you
> do not see a core dump file?
>
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/3031c2ae-6900-41e3-aceb-73e9e3f7c85fn%40googlegroups.com.

Reply via email to