Alessandro Arzilli

We didn't change anything and this issue hasn't really received any attention in the past 7 years. Our current behavior is probably fine.

This was fixed a long time ago in 6cf7a7149d35fe8c349a03caa57627860bf48ddd

My opinion remains as in https://github.com/golang/go/issues/49471#issuecomment-963879095 (i.e. in favor of this).

> It is possible with admin permissions either running a PS script or modifying the registry, but AFAIK not possible within a process. What about doing the opposite: is it...

I found this line persuasive against GOTRACEBACK=crash always using WER: > It's also the case that code might contain debug.SetTraceback("crash") intending core dumps on Unix and then accidentally get reports...

It seems to me that if you opt to send you crash dumps to microsoft during install (by not opting out) and then opt into creating a crash dump by...

> > Given that this only happens on insider builds, it isn't even that sketchy that the option is preselected. > > This wasn't an insider build; I was installing...

@alexbrainman @beoran It seems to me that there is some confusion brewing here around the term "minidump" stemming from microsoft decision to use "minidump" and "mini dump" to mean two...

> Indeed this still seems like the best solution. In theory it makes no difference, if microsoft wants to upload your core dumps they can hook MiniDumpWriteDump just like they...

> What about "minidumps" as generated by MiniDumpWriteDump? Do they work with Delve? As far as I can tell procdump.exe uses MiniDumpWriteDump to write its minidumps and Delve works with...