From: Jim Wilson <jimw@sifive.com>
To: Simon Marchi <simark@simark.ca>
Cc: hilihui@sina.com, gdb <gdb@sourceware.org>
Subject: Re: I compile gdbserver for RISCV on gdb10.1 version, and there is a error
Date: Fri, 13 Nov 2020 19:08:17 -0800 [thread overview]
Message-ID: <CAFyWVaZ2Q+1oae0+VOKtDRA60qdjM8BToKXOLWjciKQtL8f+Hw@mail.gmail.com> (raw)
In-Reply-To: <aa367527-37a7-2ff5-110e-cf840936f4af@simark.ca>
On Fri, Nov 13, 2020 at 5:13 AM Simon Marchi <simark@simark.ca> wrote:
> On 2020-11-12 9:43 p.m., hilihui@sina.com wrote:
> > ../../gdbserver/linux-riscv-low.cc:170:42: error: invalid application of
> 'sizeof' to incomplete type '__riscv_mc_q_ext_state' sizeof (struct
> __riscv_mc_q_ext_state), OPTIONAL_REGS,
> ^It seems that "__riscv_mc_q_ext_state" is not defined. How to
> resolve this question? Thanks!
> >
>
> In glibc, this type is provided here:
>
>
> https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/riscv/sys/ucontext.h;h=a4e49fe37a1397fa1babeb0dcefb77341f1e7ad1;hb=HEAD#l65
>
> And it appears to have been there since the beginning of the RISC-V
> support.
>
Since the beginning of upstream support, yes. But it was an academic
project for years before it was upstreamed and some people are stuck with
old stuff because they forked a while back and never upgraded. Or maybe
haven't upgraded yet. The ETH Zurich pulp project for instance.
> What libc is your system using?
>
He sent me private mail too. I suspect he is missing the linux kernel
RISC-V specific ptrace support also. That came after the glibc support.
Jim
next prev parent reply other threads:[~2020-11-14 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 2:43 hilihui
2020-11-13 13:13 ` Simon Marchi
2020-11-14 3:08 ` Jim Wilson [this message]
[not found] <20201116133833.1659C5D000A6@webmail.sinamail.sina.com.cn>
2020-11-16 21:55 ` Jim Wilson
2020-11-20 15:47 ` Rodney M. Bates
2020-11-20 20:37 ` Jim Wilson
2020-11-21 17:03 ` Rodney M. Bates
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=CAFyWVaZ2Q+1oae0+VOKtDRA60qdjM8BToKXOLWjciKQtL8f+Hw@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).