public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin-patches@cygwin.com
Subject: Re: [PATCH 1/5] Cygwin: Make 'ulimit -c' control writing a coredump
Date: Mon, 15 Jan 2024 13:27:45 +0000	[thread overview]
Message-ID: <3dafa845-a583-4b47-b0d6-3b16f46c8a67@dronecode.org.uk> (raw)
In-Reply-To: <ZaT-_Prh2gnn9v9y@calimero.vinschen.de>

On 15/01/2024 09:46, Corinna Vinschen wrote:
> On Jan 13 14:20, Jon Turney wrote:
>> 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.
> 
> program_invocation_short_name would be nice, but does it really matter?
> 
> Because...
> 
>> 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.
> 
> dumper/minidumper are both called with the current working directory set
> to the ... current working directory, right?  With the full pathname as
> input, and the CWD already set the same as the dumped application, they
> can easily generate any target path for the corefile they like.
> 
> Given the actual path of the corefile can be generated by the dumpers,
> the question is how to specify where to store the corefile. For instance
> 
> - no option: CWD
> - some option -c/--coredir for anywhere else
> 
> Under Linux versions using systemd, corefiles are by default not stored
> in the CWD anymore, but to /var/lib/systemd/coredump, so there is a
> use case for arbitrary corefile paths.

Yeah, I guess an option to the dumper to control where the file is 
written is probably the best way to address this, which is something 
which can perhaps be added later...


  reply	other threads:[~2024-01-15 13:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 14:09 [PATCH 0/5] Coredump under 'ulimit -c' control (v2) Jon Turney
2024-01-12 14:09 ` [PATCH 1/5] Cygwin: Make 'ulimit -c' control writing a coredump Jon Turney
2024-01-13 14:20   ` Jon Turney
2024-01-15  9:46     ` Corinna Vinschen
2024-01-15 13:27       ` Jon Turney [this message]
2024-01-15 14:28         ` Corinna Vinschen
2024-01-16 13:52           ` Jon Turney
2024-01-16 13:54             ` Corinna Vinschen
2024-01-23 14:20   ` Jon Turney
2024-01-23 14:29     ` Corinna Vinschen
2024-01-24 13:28       ` Jon Turney
2024-01-24 14:39         ` Corinna Vinschen
2024-01-25 14:50           ` Jon Turney
2024-01-25 18:21             ` Corinna Vinschen
2024-01-25 20:03               ` Jon Turney
2024-01-26 11:12                 ` Corinna Vinschen
2024-01-26 11:52                   ` Corinna Vinschen
2024-01-27 15:12                     ` Jon Turney
2024-01-29 11:16                       ` Corinna Vinschen
2024-01-12 14:09 ` [PATCH 2/5] Cygwin: Disable writing core dumps by default Jon Turney
2024-01-12 14:09 ` [PATCH 3/5] Cygwin: Define and use __WCOREFLAG Jon Turney
2024-01-12 14:09 ` [PATCH 4/5] Cygwin: Treat api_fatal() similarly to a core-dumping signal Jon Turney
2024-01-12 14:09 ` [PATCH 5/5] Cygwin: Update documentation for cygwin_stackdump Jon Turney
2024-01-12 18:44   ` Corinna Vinschen
2024-01-13 13:40     ` Jon Turney
2024-01-12 18:41 ` [PATCH 0/5] Coredump under 'ulimit -c' control (v2) Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dafa845-a583-4b47-b0d6-3b16f46c8a67@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).