public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Moritz Strübe" <moritz.struebe@siemens-energy.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Nios2, gdb: Adjust to new coredump format
Date: Fri, 19 Apr 2024 09:08:14 -0600	[thread overview]
Message-ID: <87h6fxxue9.fsf@tromey.com> (raw)
In-Reply-To: <fm-32642-202404191039253f6027d3c5d2ac7a26-pulLwC@errorhandling.siemens-energy.com> ("Moritz =?utf-8?Q?Str=C3=BCbe=22's?= message of "Fri, 19 Apr 2024 12:39:22 +0200")

>>>>> "Moritz" == Moritz Strübe <moritz.struebe@siemens-energy.com> writes:

Thank you for the patch.

Moritz> Current kernels create their coredumps using ptrace. Adjust to this new
Moritz> format.

Is there any need to support old coredumps as well; and if not, why not?

Moritz> +/* Registers not set by dump */
Moritz> +static std::set<int> notsetregs = {0, 24, 25, 30};

Should be const.

Moritz>  /* Implement the supply_regset hook for core files.  */
Moritz> -
Moritz>  static void

Spurious change.

Moritz> +  // If regno is 0 dump all registers
Moritz> +  if(regnum > 0 ){
Moritz> +    regcache->raw_supply (regnum, gregs + 4 * regnum);
Moritz> +  } else {

gdb doesn't use '//' comments and also uses a different formatting
style.

thanks,
Tom

      reply	other threads:[~2024-04-19 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240419103922.3621961-1-moritz.struebe@siemens-energy.com>
2024-04-19 10:39 ` [PATCH 1/2] Nios2, libbfd: Support new coredump .reg section Moritz Strübe
2024-04-19 15:06   ` Tom Tromey
2024-04-23 13:28   ` Luis Machado
2024-04-23 14:51     ` Sandra Loosemore
2024-04-23 15:31       ` Simon Marchi
2024-04-23 15:32       ` Luis Machado
2024-04-19 10:39 ` [PATCH 2/2] Nios2, gdb: Adjust to new coredump format Moritz Strübe
2024-04-19 15:08   ` Tom Tromey [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=87h6fxxue9.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=moritz.struebe@siemens-energy.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).