public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Djordje Todorovic <djordje.todorovic@rt-rk.com>
Cc: <binutils@sourceware.org>, <gdb-patches@sourceware.org>,
	<asowda@cisco.com>, <petar.jovanovic@rt-rk.com>,
	<nemanja.popov@rt-rk.com>,	<nikola.prica@rt-rk.com>
Subject: Re: [PATCH 2/3] BFD: Extract PID from MIPS core dump file
Date: Wed, 18 Oct 2017 13:36:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1710181258320.3886@tp.orcam.me.uk> (raw)
In-Reply-To: <1508248194-26950-2-git-send-email-djordje.todorovic@rt-rk.com>

On Tue, 17 Oct 2017, Djordje Todorovic wrote:

> On MIPS o32, n32 and n64 platforms, PID information was not
> correctly propagated from core dump file to internal GDB
> structures.  This patch fixes that behavior.
> 
> GDB needs correct PID in order to fetch value of TLS variable
> from core file.

 This is OK.  Thanks.

  Maciej

  reply	other threads:[~2017-10-18 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 13:50 [PATCH 1/3] BFD: Write Linux core PRSTATUS note into MIPS core file Djordje Todorovic
2017-10-17 13:50 ` [PATCH 2/3] BFD: Extract PID from MIPS core dump file Djordje Todorovic
2017-10-18 13:36   ` Maciej W. Rozycki [this message]
2017-10-17 13:50 ` [PATCH 3/3] Add test for fetching TLS from core file Djordje Todorovic
2017-10-18 13:37   ` Maciej W. Rozycki
2017-10-24 11:17     ` Pedro Alves
2017-10-18 13:36 ` [PATCH 1/3] BFD: Write Linux core PRSTATUS note into MIPS " Maciej W. Rozycki
2017-10-25 14:15 Djordje Todorovic
2017-10-25 14:15 ` [PATCH 2/3] BFD: Extract PID from MIPS core dump file Djordje Todorovic

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=alpine.DEB.2.00.1710181258320.3886@tp.orcam.me.uk \
    --to=macro@mips.com \
    --cc=asowda@cisco.com \
    --cc=binutils@sourceware.org \
    --cc=djordje.todorovic@rt-rk.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nemanja.popov@rt-rk.com \
    --cc=nikola.prica@rt-rk.com \
    --cc=petar.jovanovic@rt-rk.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).