[PATCH 1/5] Cygwin: Make 'ulimit -c' control writing a coredump

[Jon Turney]

On 12/01/2024 14:09, Jon Turney wrote:
> +
> +  PWCHAR cp = dumper_command;
> +  cp = wcpcpy (cp, L"\"");
> +  cp = wcpcpy (cp, dll_dir);
> +  cp = wcpcpy (cp, L"\\dumper.exe");
> +  cp = wcpcpy (cp, L"\" ");
> +  cp = wcpcpy (cp, L"\"");
> +  cp = wcpcpy (cp, global_progname);

I wonder if this should be program_invocation_short_name, so that the 
coredump is created in the cwd, rather than next to the executable.


But then, there's then no way to get similar behaviour if you decide you 
want to use minidumps instead (by setting 
CYGWIN="error_start=minidumper"), as the first argument to 
dumper/minidump is the full path to the program (to match the 'prog 
procID' style of invoking gdb), but they only use it to add an 
.core/.dmp extension to name the file to write.

I guess that could by fixed by adding an option to the dumpers to strip 
paths, or more control about how the JIT command is formatted.