From: Pedro Alves <palves@redhat.com>
To: Stafford Horne <shorne@gmail.com>,
GNU Binutils <binutils@sourceware.org>
Cc: GDB patches <gdb-patches@sourceware.org>,
Openrisc <openrisc@lists.librecores.org>,
Waldemar Brodkorb <wbx@openadk.org>,
Kevin Buettner <kevinb@redhat.com>
Subject: Re: [RESEND PATCH] gdb/or1k: Add linux debugging support
Date: Tue, 11 Dec 2018 12:40:00 -0000 [thread overview]
Message-ID: <e1e54818-9a25-1cc3-c04d-86cfc0c485bf@redhat.com> (raw)
In-Reply-To: <20181207063909.15365-1-shorne@gmail.com>
On 12/07/2018 06:39 AM, Stafford Horne wrote:
> (Resend to include binutils list)
>
> Up until now OpenRISC GDB only has supported bare metal debugging. This
> patch adds linux userspace debugging and core dump analysis support.
Could you send a patch to documents this addition in the gdb/NEWS file?
https://sourceware.org/gdb/wiki/ContributionChecklist#Documentation
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-12-11 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 6:39 Stafford Horne
2018-12-07 13:41 ` Kevin Buettner
2018-12-07 15:18 ` Nick Clifton
2018-12-07 22:31 ` Stafford Horne
2018-12-11 12:40 ` Pedro Alves [this message]
2018-12-11 21:30 ` Stafford Horne
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=e1e54818-9a25-1cc3-c04d-86cfc0c485bf@redhat.com \
--to=palves@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.com \
--cc=wbx@openadk.org \
/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