From: Thorsten Glaser <tg@mirbsd.de>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: Not sure how to debug this one.
Date: Sat, 17 Feb 2024 23:09:24 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2402172305090.9009@herc.mirbsd.org> (raw)
In-Reply-To: <ZdEo_58yYjO6wl8y@snips.stderr.spb.ru>
Valery Ushakov dixit:
>comments (*ugh*), but I *think* sigsetjmp clobbers caller's r8.
>
>r8 is callee saved.
Say, is there a handy list of which registers are preserved
or clobbered across function calls like the one for syscalls
from Linux man-pages’ syscall(2) for all arches?
I have indeed chased this same problem on unfamiliar arches
often enough as well…
bye,
//mirabilos
--
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival
next prev parent reply other threads:[~2024-02-17 23:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 1:48 [musl] " Rob Landley
2024-02-17 3:23 ` [musl] Re: [Toybox] " Mouse
2024-02-17 13:32 ` Rob Landley
2024-02-17 15:01 ` [musl] " Thorsten Glaser
2024-02-17 15:21 ` [musl] " Mouse
2024-02-17 17:02 ` [musl] " Rich Felker
2024-02-17 21:45 ` [musl] " Valery Ushakov
2024-02-17 23:09 ` Thorsten Glaser [this message]
2024-02-18 12:15 ` [musl] " Valery Ushakov
2024-02-18 22:51 ` [musl] " Thorsten Glaser
2024-02-18 1:34 ` Rich Felker
2024-02-18 1:40 ` Rich Felker
2024-02-18 12:55 ` Valery Ushakov
2024-02-18 14:33 ` Rich Felker
2024-02-18 15:06 ` Valery Ushakov
2024-02-18 20:33 ` Rich Felker
2024-02-19 11:00 ` Valery Ushakov
2024-02-19 17:54 ` Rob Landley
2024-02-19 23:05 ` Rich Felker
2024-02-18 12:47 ` Valery Ushakov
2024-02-19 13:12 ` Rob Landley
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=Pine.BSM.4.64L.2402172305090.9009@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).