From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cmo-0001.xspmail.jp ([202.238.198.169]) by ewsd; Thu Jul 9 19:31:38 EDT 2020 Received: from cmr-0000.xspmail.jp ([202.238.198.117]) by cmo with ESMTP id tfspj5kJJL3Uqtg0tjMKFd; Fri, 10 Jul 2020 08:31:35 +0900 Received: from pi4.jitaku.localdomain ([180.147.121.119]) by cmr with ESMTPA id tg0sj2WkIoVEWtg0sjYt6y; Fri, 10 Jul 2020 08:31:35 +0900 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hera.eonet.ne.jp; s=x01; t=1594337495; i=kokamoto@hera.eonet.ne.jp; bh=j1yqvWDnDfqelk66EDkWvJ0+K7xqW4KVnyRR+wLw3wM=; h=To:Subject:Date:From:In-Reply-To; b=hUE7YV0hGrYf2EiqtG/e7lZBGxkQMOcTj+O8FcP1d+wruOFoG5w0dtUH/hm3WSMxa VoAZTVs19slRm9S4mi9usGdfvDfjj9NtPAdyD5DcvcqcTAw/OQwQ3Vyx+bsfiH3DqL YAtAinU4I7WIJmMZfGCSpPNscVWEFGQdX/9c1akzLyKJgkkiG6rXNGjLm1nb5EJ7jr 3c1EIOduklp8kvCtySmOwiPQt3W4VICGMP48fRaXiLRBqRW5W68HL6UQ2E8boKlnWG X0D2vejVkR1aE9/ipPETtN2ZdrelHsK4iDv7sA9WivrKMfGF7gBvGsLF9JpvNgDLAS w9hOA8ChXk+iw== Message-ID: <6395C3F2B95C8613FF96D424940F4713@hera.eonet.ne.jp> To: 9front@9front.org Subject: Re: [9front] x509.c for ape in libsec.a Date: Fri, 10 Jul 2020 08:31:32 +0900 From: kokamoto@hera.eonet.ne.jp In-Reply-To: <8368654C67EEBB185E5A98F6D3DD7C6D@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: transactional property dependency TOR software property controller 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.