From: Jim Wilson <jimw@sifive.com>
To: hilihui@sina.com
Cc: Simon Marchi <simark@simark.ca>, gdb <gdb@sourceware.org>
Subject: Re: Re: Re: I compile gdbserver for RISCV on gdb10.1 version, and there is a error
Date: Wed, 18 Nov 2020 17:04:53 -0800 [thread overview]
Message-ID: <CAFyWVaaszDY-D0fLKP5WSNOUhKqm+7EVCd=_08aM_G2T54vyqw@mail.gmail.com> (raw)
In-Reply-To: <20201117020745.B044518C0098@webmail.sinamail.sina.com.cn>
On Mon, Nov 16, 2020 at 6:07 PM <hilihui@sina.com> wrote:
> Where is your patches?
>
In the upstream linux kernel. But they were added in Summer/Fall 2018. If
you have an old linux kernel release, then you won't have them. They
should be in the linux kernel mailing list, but I don't know of an easy way
to search that offhand. If you do a git log on a recent linux kernel clone
and then look for jimw@sifive.com you will see 4 patches. The first one,
futex, was for glibc. The other 3 are for gdb. You can then use git diff
to extract the patches. Or cherry-pick them or whatever.
Jim
next parent reply other threads:[~2020-11-19 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201117020745.B044518C0098@webmail.sinamail.sina.com.cn>
2020-11-19 1:04 ` Jim Wilson [this message]
2020-11-19 12:12 ` Jan Vrany
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='CAFyWVaaszDY-D0fLKP5WSNOUhKqm+7EVCd=_08aM_G2T54vyqw@mail.gmail.com' \
--to=jimw@sifive.com \
--cc=gdb@sourceware.org \
--cc=hilihui@sina.com \
--cc=simark@simark.ca \
/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).