public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Lukasz Stelmach <l.stelmach@samsung.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: libc-alpha@sourceware.org,  Andrew Waterman <andrew@sifive.com>,
	m.moscicki2@samsung.com
Subject: Re: RISC-V: sys/user.h
Date: Tue, 13 Dec 2022 18:01:05 +0100	[thread overview]
Message-ID: <dleftj359j44ry.fsf%l.stelmach@samsung.com> (raw)
In-Reply-To: <mhng-d1ff5609-2f0a-4179-aec2-b099de0b20aa@palmer-ri-x1c9> (Palmer Dabbelt's message of "Fri, 09 Dec 2022 16:26:03 -0800 (PST)")

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

It was <2022-12-09 pią 16:26>, when Palmer Dabbelt wrote:
> On Fri, 09 Dec 2022 13:36:05 PST (-0800), l.stelmach@samsung.com wrote:
>> It was <2022-12-09 pią 09:07>, when Palmer Dabbelt wrote:
>>> On Fri, 09 Dec 2022 08:36:33 PST (-0800), l.stelmach@samsung.com wrote:
>>>> Has sysdeps/unix/sysv/linux/riscv/sys/user.h been deliberately left
>>>> empty? Why, unlike x86/aarch64/arm, riscv haven't got it's register
>>>> structures defined there?
>>>
>>> We don't have a "struct user_regs_struct", IIUC that's for the old
>>> flavor of ptrace-based register handling ({GET,SET}REGS vs
>>> {GET,SET}REGSET).  So I think having it empty is the correct thing
>>> to do.
>>
>>
>> Thanks, this is a precious hint. Now, I know where to look around.
>
> Those definitions are in
> <sysdeps/unix/sysv/linux/riscv/sys/ucontext.h>

I missed this one

> (and also in Linux).

but found this <asm/ptrace.h>.


It's not that we didn't have these definitions at all, but because
we'are building a small tool that we want to run on different
architectures, we're looking into how to access the regiester data in
core dumps (we need to read one or two values) without lengthy #if#elifs
around the code and includes. We just want this tiny piece of code of
ours to be noice (-;

Thanks for help (-:
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2022-12-13 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221209163647eucas1p226b7c480e55c23c51176d610b2adae66@eucas1p2.samsung.com>
2022-12-09 16:36 ` Lukasz Stelmach
2022-12-09 17:07   ` Palmer Dabbelt
     [not found]     ` <CGME20221209213619eucas1p19f6cdc951c8071488cf12ca618911504@eucas1p1.samsung.com>
2022-12-09 21:36       ` Lukasz Stelmach
2022-12-10  0:26         ` Palmer Dabbelt
     [not found]           ` <CGME20221213170125eucas1p1762e0d6aa0b65bbd3d9f7ad2ce31a590@eucas1p1.samsung.com>
2022-12-13 17:01             ` Lukasz Stelmach [this message]

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=dleftj359j44ry.fsf%l.stelmach@samsung.com \
    --to=l.stelmach@samsung.com \
    --cc=andrew@sifive.com \
    --cc=libc-alpha@sourceware.org \
    --cc=m.moscicki2@samsung.com \
    --cc=palmer@dabbelt.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).