From: Dmad <dmadhatr@sdf.org>
To: 9front@9front.org
Subject: Re:SOLVED [9front] 9Front Drawterm Code 139 Sig 11 SIGSEGV
Date: Sun, 24 Sep 2023 03:24:09 +0000 (UTC) [thread overview]
Message-ID: <3157c339-4797-604c-34f6-306dc2967107@sdf.org> (raw)
In-Reply-To: <0560683a-9d4a-7361-b6d8-edb5155808f0@sdf.org>
On Sun, 24 Sep 2023, Dmad wrote:
> Date: Sun, 24 Sep 2023 03:11:13 +0000 (UTC)
> From: Dmad <dmadhatr@sdf.org>
> Reply-To: 9front@9front.org
> To: 9front@9front.org
> Subject: Re: [9front] 9Front Drawterm Code 139 Sig 11 SIGSEGV
>
> On Sun, 24 Sep 2023, Sigrid Solveig Hafl?nud?ttir wrote:
>
>> Date: Sun, 24 Sep 2023 04:28:27 +0200
>> From: Sigrid Solveig Hafl?nud?ttir <sigrid@ftrv.se>
>> Reply-To: 9front@9front.org
>> To: 9front@9front.org
>> Subject: Re: [9front] 9Front Drawterm Code 139 Sig 11 SIGSEGV
>>
>> Try to replace the entirety of your amd64/tas.c "tas" function with just
>> "return __atomic_test_and_set(x, __ATOMIC_ACQ_REL);", as appears in
>> arm64/tas.c
>> See if that helps.
>>
>>
>
> Backed up tas.c
> Replaced tas function with just 'return' ... from arm64 tas.c to amd84
> Recompiled
> ./drawterm -h IP -a IP -u glenda
> No crash, but no RIO just yet.
> Progress!
> Thanks!
>
> dmadhatr@sdf.org
> SDF Public Access UNIX System - http://sdf.org
>
Retarted drawterm session, removed -r option and was able to get rio
running from 9p.sdf.org without any crash/segsdev 11 or stack issue.
Replacing the tas function for AMD64 before recompiling appears to have
worked.
Cheers and thanks again, appreciated.
dmadhatr@sdf.org
SDF Public Access UNIX System - http://sdf.org
next prev parent reply other threads:[~2023-09-24 3:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 19:11 Dmad
2023-09-22 19:55 ` hiro
2023-09-23 13:44 ` Dmad
2023-09-23 1:10 ` Amavect
2023-09-23 13:52 ` Dmad
2023-09-23 16:04 ` Dmad
2023-09-23 17:32 ` Dmad
2023-09-24 1:39 ` Dmad
2023-09-24 2:28 ` Sigrid Solveig Haflínudóttir
2023-09-24 2:40 ` Dmad
2023-09-24 3:11 ` Dmad
2023-09-24 3:24 ` Dmad [this message]
2023-09-24 4:44 ` Amavect
2023-09-24 15:13 ` Dmad
2023-09-27 4:45 ` Amavect
2023-09-25 13:54 ` Xiao-Yong Jin
2023-09-25 14:47 ` Dmad
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=3157c339-4797-604c-34f6-306dc2967107@sdf.org \
--to=dmadhatr@sdf.org \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).