From: ori@eigenstate.org
To: kokamoto@hera.eonet.ne.jp, 9front@9front.org
Subject: Re: [9front] x509.c for ape in libsec.a
Date: Thu, 9 Jul 2020 17:27:55 -0700 [thread overview]
Message-ID: <EE200D85904ABD35EB799A3339DFC205@eigenstate.org> (raw)
In-Reply-To: <6395C3F2B95C8613FF96D424940F4713@hera.eonet.ne.jp>
> This seems to be so from very old, the timestamp of Feb 1, 2018
> does fail, too.
>
> Kenji
>
>>> More precisely,
>>> for stringobject.c:
>>> static PyObject *
>>> SubString_new_object_or_empty(SubString *str)
>>> {
>>> if (str->ptr ==((void *)0)) {
>>> return PyString_FromStringAndSize(((void *)0), 0);
>>> }
>>> return PyString_FromStringAndSize(str->ptr, str->end - str->cpp 612: suicide: sys: trap: fault write addr=0xdeffeff4 pc=0x00008705
>>>
>>> The last line shows PyString_FromStringAndSize() function in cpython/Objects/stringobject.c,
>>> and to do return (PyObject *) op;
>>> Probably, this 'op' is not on the memory...
>>>
>>> I replaced /386/bin/cpp by that from 9legacy'e one, and recompiled.
>>> Yes, it's Ok with no problem.
>>>
>>> Therefore 9front's /386/bin/cpp has some problem, I think.
>>>
>>> Kenji
>>
>> Yes. I'll look into it.
That's surprising, honestly -- I did a lot of surgery on cpp recently
to make it much more standard compliant, and I wouldn't be surprised if
I missed a subtle case.
What's happening right now is that we're recursing infinitely when we
expand *something*.
I'm not sure what yet, but I can reproduce it, so I should be able to
get a fix from the information I have.
I'm guessing that the fix will be shuffling around the way that we
build up our hide-sets.
next prev parent reply other threads:[~2020-07-10 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 5:37 kokamoto
2020-07-02 4:54 ` [9front] " kokamoto
2020-07-02 14:48 ` Ori Bernstein
2020-07-04 0:39 ` kokamoto
2020-07-08 5:19 ` kokamoto
2020-07-09 4:19 ` kokamoto
2020-07-09 4:25 ` ori
2020-07-09 23:31 ` kokamoto
2020-07-10 0:23 ` kokamoto
2020-07-10 0:27 ` ori [this message]
2020-07-10 0:53 ` Dr. Kenji Okamoto
2020-07-10 1:31 ` kokamoto
2020-07-10 4:12 ` ori
2020-07-10 4:36 ` kokamoto
2020-07-13 1:39 ` ori
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=EE200D85904ABD35EB799A3339DFC205@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=kokamoto@hera.eonet.ne.jp \
/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).