From: Simon Marchi <simark@simark.ca>
To: Paul Mathieu <paulmathieu@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add support for handling core dumps on arm-none-eabi
Date: Fri, 2 Oct 2020 22:24:12 -0400 [thread overview]
Message-ID: <40b649d6-c2a7-5e1b-b411-879280ed79c6@simark.ca> (raw)
In-Reply-To: <CAO_VGhpr3Qghp77wnizpu54wAkeRgNMBzR3PK8YpfL5pVNuTPQ@mail.gmail.com>
On 2020-10-02 8:35 p.m., Paul Mathieu wrote:
> Thanks for the feedback Simon!
> I did send a new version of that patch as a reply to Luis' feedback, you seem to have commented on the first one.
> Should I have sent that patch in a different thread?
Ah sorry, I didn't see it buried in your response. It's fine, although
doing proper version helps tracking the different versions.
>
> Some quick comments, just skimming the patch. I won't comment about
> indentation issue, because I don't know if it has been modified by the
> email client.
>
> I support what Luis has already said, it needs to be documented what
> this format is, where it is defined/specified, who produces it, etc.
>
>
> I'm not sure how (and where) this could be documented, are there examples of such documentation?
> Since I couldn't find any prior art for bare metal targets, I went for something that I assumed was a standard core file format.
I'm not very well-versed in the domain of core files, but it is my
understanding that the format is quite platform dependent. The
container is often an ELF file with notes. But the format of those
notes' content varies from one platform to another. For example, the
layout of how registers are saved in a Linux core file differs from the
layout of registers in a FreeBSD core. Similarly, for bare-metal, the
tool you are using to generate the core decides of a certain layout,
which could be different from the layout chosen by another tool.
Therefore, I think it's important to describe what the layout expected
by your code is (what tool/platform produces it).
It is a good start to document it somewhere in the code. We can then
think if it would be relevant to document it in the user manual as well
(we'll have a better idea when we understand better where these cores
come from).
Simon
next prev parent reply other threads:[~2020-10-03 2:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 17:32 Paul Mathieu
2020-10-02 17:51 ` Luis Machado
2020-10-02 21:54 ` Paul Mathieu
2020-10-02 21:59 ` Simon Marchi
2020-10-03 3:57 ` Simon Marchi
2020-10-03 18:14 ` [PATCH v2] " Paul Mathieu
2020-10-04 17:30 ` Paul Mathieu
2020-10-04 23:41 ` Simon Marchi
2020-10-06 4:32 ` Paul Mathieu
2020-10-06 12:45 ` Luis Machado
2020-10-06 14:29 ` Simon Marchi
2020-10-06 16:59 ` Paul Mathieu
2020-10-06 17:37 ` Simon Marchi
2020-10-05 12:58 ` Luis Machado
2020-10-05 13:24 ` Alan Hayward
2020-10-02 23:55 ` [PATCH] " Simon Marchi
2020-10-03 0:35 ` Paul Mathieu
2020-10-03 2:24 ` Simon Marchi [this message]
2020-10-17 0:02 Fredrik Hederstierna
2020-10-19 2:08 ` Simon Marchi
2020-10-19 13:13 ` Luis Machado
2020-10-19 13:15 ` Alan Hayward
2020-10-19 15:25 ` Paul Mathieu
2020-10-20 11:41 ` Fredrik Hederstierna
2020-10-20 12:39 ` Simon Marchi
2020-10-20 14:00 ` Fredrik Hederstierna
2020-10-20 15:04 ` Simon Marchi
2020-10-20 22:05 ` Fredrik Hederstierna
2020-10-20 23:06 ` Simon Marchi
2020-10-22 0:52 ` Fredrik Hederstierna
2020-10-22 1:24 ` Simon Marchi
2020-10-22 1:49 ` Simon Marchi
2020-10-22 22:32 ` Fredrik Hederstierna
2020-10-23 0:37 ` Simon Marchi
2020-10-25 21:06 ` Fredrik Hederstierna
2020-10-26 11:24 ` Luis Machado
2020-10-26 15:49 ` Fredrik Hederstierna
2020-10-27 16:53 ` Paul Mathieu
2021-01-14 12:36 ` Fredrik Hederstierna
2021-01-14 12:50 ` Luis Machado
2021-01-18 11:09 ` Andrew Burgess
2021-01-18 14:01 ` Luis Machado
2021-01-18 11:01 ` Andrew Burgess
2021-06-22 2:16 ` Mike Frysinger
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=40b649d6-c2a7-5e1b-b411-879280ed79c6@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=paulmathieu@google.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).