From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] x509.c for ape in libsec.a
Date: Thu, 9 Jul 2020 13:19:26 +0900 [thread overview]
Message-ID: <DD3D1A72A441D1560FF09EEEE1EFD3AD@hera.eonet.ne.jp> (raw)
In-Reply-To: <702D55686C960FDA9FFE71F48D57ADAA@hera.eonet.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
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
[-- Attachment #2: Type: message/rfc822, Size: 3158 bytes --]
From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] x509.c for ape in libsec.a
Date: Wed, 8 Jul 2020 14:19:17 +0900
Message-ID: <702D55686C960FDA9FFE71F48D57ADAA@hera.eonet.ne.jp>
I recopied wright python2.7.6 source tree, and have the same
problem so on.
stringobject.c and unicodeobject.c
The errors may be related to cpp, such like:
substargs()->maketokenrow()->domalloc()->malloc()->poolalloc()->p->lock(p);
acid of cpp for those files indivcate different things:
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
for unicodeobject.c:
static PyObject *
getitem_sequence(PyObject *obj, Py_ssize_t idx)
{
return PySequence_GetItem(obj, idx);
}
Kenji
static PyObjecpp 766: suicide: sys: trap: fault write addr=0xdeffeff4 pc=0x00008705
>> What were the problems you ran into compiling them?
>
> Sorry, I copied wrong cpython source tree from that I compiled
> on 9legacy, which is python2.7.6 not 2.7.9.
next prev parent reply other threads:[~2020-07-09 4:19 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 [this message]
2020-07-09 4:25 ` ori
2020-07-09 23:31 ` kokamoto
2020-07-10 0:23 ` kokamoto
2020-07-10 0:27 ` ori
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=DD3D1A72A441D1560FF09EEEE1EFD3AD@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--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).