public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Libor Bukata <libor.bukata@oracle.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC][PATCH 2/3] [bfd] Add Solaris specific ELF note processing.
Date: Wed, 14 Jul 2021 20:46:20 -0400	[thread overview]
Message-ID: <d592355c-a715-a8f8-765e-4f4162520094@polymtl.ca> (raw)
In-Reply-To: <MWHPR1001MB222429E4FC4CF3E1CA83FF2AFF139@MWHPR1001MB2224.namprd10.prod.outlook.com>

On 2021-07-14 9:18 a.m., Libor Bukata via Gdb-patches wrote:
> From 3dafe7a64cd42a017b58d916e3055d993173563a Mon Sep 17 00:00:00 2001
> From: Libor Bukata <libor.bukata@oracle.com>
> Date: Wed, 14 Jul 2021 11:53:56 +0200
> Subject: [PATCH 2/3] [bfd] Add Solaris specific ELF note processing.
> 
> Added elfcore_grok_solaris_note function that enables to
> obtain process status, register values, and program info.
> 
> Tested on Solaris x86_64/sparcv9 and Linux x86_64.
> 
> bfd/ChangeLog:
> 
> 2021-07-12  Libor Bukata <libor.bukata@oracle.com>
> 
>   * elf-bfd.h (elf_backend_grok_lwpstatus): Added function.
>   * elfxx-target.h (elf_backend_data): Updated ELF backend data.
>   * bfd/elf.c (elfcore_grok_solaris_note): Solaris specific ELF
>   note parser. Better GDB's coredump analysis on Solaris...
>   (call_elfcore_grok_solaris_note): Helper function.
>   (elf_parse_notes): Added "CORE" groker element.

Hi,

This should be sent to binutils@sourceware.org.

Simon

      reply	other threads:[~2021-07-15  0:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 13:18 Libor Bukata
2021-07-15  0:46 ` Simon Marchi [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=d592355c-a715-a8f8-765e-4f4162520094@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=libor.bukata@oracle.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).