public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Simon Sobisch <simonsobisch@gnu.org>,
	Simon Sobisch via Gdb <gdb@sourceware.org>
Subject: Re: Is corefile support for missing on Win32?
Date: Thu, 9 Jun 2022 17:20:44 +0100	[thread overview]
Message-ID: <87eba601-e753-02ac-0645-45c09377cac6@palves.net> (raw)
In-Reply-To: <e73f4662-7614-c05a-77dd-bd65ac858cb5@gnu.org>

On 2022-06-07 20:30, Simon Sobisch via Gdb wrote:
> Testing with MSYS2 generated mingw64 gcc 12.1 + gdb 12.1 resulted in "everything working" ...until I needed to create a core file.
> 
> (gdb) show arch
> The target architecture is set to "auto" (currently "i386:x86-64").
> (gdb) gcore test.core
> warning: cannot close "test.core": invalid operation
> Can't create a corefile
> 
> (with gnutarget auto, pei-x86-64 and pe-x86-64)
> 
> I see that the first error message comes from
>   gdb/gdb_bfd.c (gdb_bfd_close_warning)
> and the second from the default implementation
>   gdb/exec.c (make_corefile_notes)
> 
> 
> This issue seems to exists for longer as some SO question [1] asked about this over 5 years ago.
> 
> Further testing showed the same issue with same tools in MinGW x86 and with "good old MinGW" using GDB 7.6.1 / GCC 9.2.
> 
> Testing with cygwin-x64 (GDB 11.2) shows the same result.
> 

Native Windows GDB was never able to generate cores.  Basically because cores are ELF objects,
while Windows is PE, so it's kind of a foreign thing.

However, Cygwin comes with a separate utility that is able to dump cores in ELF format, and
Windows GDB is actually able to read those.  This utility is called "dumper".  See here:

  https://www.cygwin.com/cygwin-ug-net/dumper.html

Sources are here:

  https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/utils/dumper.cc

If someone wanted to work on it, I don't see any obstacle to GDB's gcore command
itself generating an ELF core in the exact same format.

> I guess the system's minidump format cannot be processed with GDB, can it?

Unfortunately not.  Christian Biesinger did write a patch to add support for it while ago, though:

  https://sourceware.org/git/?p=binutils-gdb.git;a=shortlog;h=refs/heads/users/cbiesinger/minidump

AFAIK, this was never finished/contributed for proper inclusion, and I don't know how far
that is to being complete.

  reply	other threads:[~2022-06-09 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 19:30 Simon Sobisch
2022-06-09 16:20 ` Pedro Alves [this message]
2023-02-07 10:35   ` Simon Sobisch
2023-02-07 20:18     ` Christian Biesinger
2023-02-08 16:28       ` Hannes Domani

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=87eba601-e753-02ac-0645-45c09377cac6@palves.net \
    --to=pedro@palves.net \
    --cc=gdb@sourceware.org \
    --cc=simonsobisch@gnu.org \
    /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).