From: Hannes Domani <ssbssa@yahoo.de>
To: Simon Sobisch <simonsobisch@gnu.org>,
Christian Biesinger <cbiesinger@google.com>
Cc: Pedro Alves <pedro@palves.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Is corefile support for missing on Win32?
Date: Wed, 8 Feb 2023 16:28:46 +0000 (UTC) [thread overview]
Message-ID: <1732134213.367256.1675873726952@mail.yahoo.com> (raw)
In-Reply-To: <CAPTJ0XHefq3awcxGV_vXLBj47huxgAU16zup95UueEDXDUNW2Q@mail.gmail.com>
Am Dienstag, 7. Februar 2023, 21:19:29 MEZ hat Christian Biesinger via Gdb <gdb@sourceware.org> Folgendes geschrieben:
> On Tue, Feb 7, 2023 at 5:36 AM Simon Sobisch <simonsobisch@gnu.org> wrote:
> >
> > This is especially a call to Christian Biesinger to ask if there was any
> > more work on "supporting minidump with GDB"; but there's more content
> > "inline" in the text, too.
>
> Yes unfortunately I have not continued work on that branch. It is more
> of a proof of concept at this point, most types of data are not
> implemented yet, outside of registers and memory.
>
> I also did not love the way I integrated minidump support with the
> rest of GDB. It was done as a new BFD target and converted minidump
> info to ELF coredump-style in-memory sections. That's fine for memory
> but feels awkward for register data... and possibly requires special
> code for each arch/OS combination (e.g. amd64_linux_gregset_reg_offset
> may be different from the Windows and Mac equivalent, and of course is
> different from x86 and ARM)
>
> I haven't looked into mapping loaded DLLs and threads.
>
> Realistically this will need someone else to pick up this work, unless
> I unexpectedly find myself with a large amount of free time.
>
> (Obviously this does not support PDB debug symbols, another project
> that would be interesting to do. Perhaps it could use the Python
> symbol support for which I saw patches go by the other week)
>
> In the meantime you may be interested in this tool:
> https://chromium.googlesource.com/chromium/src.git/+/main/docs/linux/minidump_to_core.md
I implemented minidump support for gdb some time ago.
The main commits are these:
https://github.com/ssbssa/gdb/compare/b4535a016c98a5a15622bbdcbcd845e3387413f5...8961acde2b6521f629ddaa1880ba312b998351eb
Since I didn't know any better, I just put the code into coffgen.c, which
was probably not a good idea.
You can try it out with my builds here:
https://github.com/ssbssa/gdb/releases
Regards
Hannes
prev parent reply other threads:[~2023-02-08 16:28 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
2023-02-07 10:35 ` Simon Sobisch
2023-02-07 20:18 ` Christian Biesinger
2023-02-08 16:28 ` Hannes Domani [this message]
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=1732134213.367256.1675873726952@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=pedro@palves.net \
--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).