From: Djordje Todorovic <djordje.todorovic@rt-rk.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
"nemanja.popov@rt-rk.com" <nemanja.popov@rt-rk.com>,
petar.jovanovic@rt-rk.com,
"Ananthakrishna Sowda (asowda)" <asowda@cisco.com>,
Nikola Prica <nikola.prica@rt-rk.com>
Subject: Re: [PATCH 0/3] Fix issues with writing Linux core PRSTATUS note on MIPS o32, n32 and n64 into core file
Date: Tue, 17 Oct 2017 13:57:00 -0000 [thread overview]
Message-ID: <974b0468-f6e0-f268-0a47-5fb89f2256f6@rt-rk.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1710171449200.3886@tp.orcam.me.uk>
Hi Maciej,
>Native presumably, right? I'll push them through n32 and n64 native
>testing for you then and just smoke-test your newly added case with a
>cross-debugger and a remote target (where no core file generation is
>currently supported).
Yes, native. Thanks a lot!
Thanks,
Djordje
next prev parent reply other threads:[~2017-10-17 13:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 13:47 Djordje Todorovic
2017-10-17 13:55 ` Maciej W. Rozycki
2017-10-17 13:57 ` Djordje Todorovic [this message]
2017-10-25 14:15 ` Djordje Todorovic
2017-10-25 22:40 ` Maciej W. Rozycki
2017-10-26 11:22 ` Djordje Todorovic
2017-10-30 13:44 ` Maciej W. Rozycki
2017-10-30 14:12 ` Maciej W. Rozycki
2017-11-03 13:05 ` Djordje Todorovic
2017-11-07 21:59 ` Maciej W. Rozycki
2017-11-08 10:10 ` Pedro Alves
2017-11-08 21:23 ` Maciej W. Rozycki
2017-11-08 21:24 ` [committed v7 1/3] BFD: Write Linux core PRSTATUS note into MIPS " Maciej W. Rozycki
2017-11-08 21:24 ` [committed v7 2/3] BFD: Extract PID from MIPS core dump file Maciej W. Rozycki
2017-11-08 21:26 ` [committed v7 3/3] Add test for fetching TLS from core file Maciej W. Rozycki
2017-11-09 10:32 ` [PATCH 0/3] Fix issues with writing Linux core PRSTATUS note on MIPS o32, n32 and n64 into " Djordje Todorovic
2017-11-09 22:41 ` Maciej W. Rozycki
2017-11-07 21:31 ` Maciej W. Rozycki
2017-11-08 9:56 ` Pedro Alves
2017-11-08 18:41 ` Maciej W. Rozycki
2017-10-27 15:00 ` Pedro Alves
2017-10-30 13:38 ` Maciej W. Rozycki
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=974b0468-f6e0-f268-0a47-5fb89f2256f6@rt-rk.com \
--to=djordje.todorovic@rt-rk.com \
--cc=asowda@cisco.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@mips.com \
--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).