From fijall at gmail.com  Mon Feb  1 03:59:07 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Mon, 1 Feb 2016 09:59:07 +0100
Subject: [pypy-dev] [pypy-commit] pypy py3.3: Fix unicode.capitalize()
 test to pass with CPython3.3, 
In-Reply-To: <56ae9bdc.a3abc20a.ddb4.ffff9400@mx.google.com>
References: <56ae9bdc.a3abc20a.ddb4.ffff9400@mx.google.com>
Message-ID: <CAK5idxQNGTPzLZdzf563tgz=4Z1=5qrp0wGbfuaGo4B50BKRkw@mail.gmail.com>

Those things are probably why pypy3 is so much slower than pypy2

On Mon, Feb 1, 2016 at 12:42 AM, amauryfa <pypy.commits at gmail.com> wrote:
> Author: Amaury Forgeot d'Arc <amauryfa at gmail.com>
> Branch: py3.3
> Changeset: r82021:44aa48e4d16a
> Date: 2016-02-01 00:31 +0100
> http://bitbucket.org/pypy/pypy/changeset/44aa48e4d16a/
>
> Log:    Fix unicode.capitalize() test to pass with CPython3.3, and implement
>         it for PyPy. Probably not the fastest implementation...
>
> diff --git a/pypy/objspace/std/test/test_unicodeobject.py b/pypy/objspace/std/test/test_unicodeobject.py
> --- a/pypy/objspace/std/test/test_unicodeobject.py
> +++ b/pypy/objspace/std/test/test_unicodeobject.py
> @@ -217,7 +217,7 @@
>          # check that titlecased chars are lowered correctly
>          # \u1ffc is the titlecased char
>          assert ('\u1ff3\u1ff3\u1ffc\u1ffc'.capitalize() ==
> -                '\u1ffc\u1ff3\u1ff3\u1ff3')
> +                '\u03a9\u0399\u1ff3\u1ff3\u1ff3')
>          # check with cased non-letter chars
>          assert ('\u24c5\u24ce\u24c9\u24bd\u24c4\u24c3'.capitalize() ==
>                  '\u24c5\u24e8\u24e3\u24d7\u24de\u24dd')
> diff --git a/pypy/objspace/std/unicodeobject.py b/pypy/objspace/std/unicodeobject.py
> --- a/pypy/objspace/std/unicodeobject.py
> +++ b/pypy/objspace/std/unicodeobject.py
> @@ -155,13 +155,16 @@
>          return unicodedb.islinebreak(ord(ch))
>
>      def _upper(self, ch):
> -        return unichr(unicodedb.toupper(ord(ch)))
> +        return u''.join([unichr(x) for x in
> +                         unicodedb.toupper_full(ord(ch))])
>
>      def _lower(self, ch):
> -        return unichr(unicodedb.tolower(ord(ch)))
> +        return u''.join([unichr(x) for x in
> +                         unicodedb.tolower_full(ord(ch))])
>
>      def _title(self, ch):
> -        return unichr(unicodedb.totitle(ord(ch)))
> +        return u''.join([unichr(x) for x in
> +                         unicodedb.totitle_full(ord(ch))])
>
>      def _newlist_unwrapped(self, space, lst):
>          return space.newlist_unicode(lst)
> _______________________________________________
> pypy-commit mailing list
> pypy-commit at python.org
> https://mail.python.org/mailman/listinfo/pypy-commit

From amauryfa at gmail.com  Mon Feb  1 05:06:05 2016
From: amauryfa at gmail.com (Amaury Forgeot d'Arc)
Date: Mon, 1 Feb 2016 11:06:05 +0100
Subject: [pypy-dev] [pypy-commit] pypy py3.3: Fix unicode.capitalize()
 test to pass with CPython3.3, 
In-Reply-To: <CAK5idxQNGTPzLZdzf563tgz=4Z1=5qrp0wGbfuaGo4B50BKRkw@mail.gmail.com>
References: <56ae9bdc.a3abc20a.ddb4.ffff9400@mx.google.com>
 <CAK5idxQNGTPzLZdzf563tgz=4Z1=5qrp0wGbfuaGo4B50BKRkw@mail.gmail.com>
Message-ID: <CAGmFidZ_j+XyagqONPduwYF18zANtW_f_ZCOg=4Sf8M9Mj89JA@mail.gmail.com>

2016-02-01 9:59 GMT+01:00 Maciej Fijalkowski <fijall at gmail.com>:

> Those things are probably why pypy3 is so much slower than pypy2
>

Agreed. I prefer to have things correct first, and work on performance
later.
For this particular case though, do you have an idea on how to improve this?
Pass the UnicodeBuilder to unicodedb.toupper_full()?


>
> On Mon, Feb 1, 2016 at 12:42 AM, amauryfa <pypy.commits at gmail.com> wrote:
> > Author: Amaury Forgeot d'Arc <amauryfa at gmail.com>
> > Branch: py3.3
> > Changeset: r82021:44aa48e4d16a
> > Date: 2016-02-01 00:31 +0100
> > http://bitbucket.org/pypy/pypy/changeset/44aa48e4d16a/
> >
> > Log:    Fix unicode.capitalize() test to pass with CPython3.3, and
> implement
> >         it for PyPy. Probably not the fastest implementation...
> >
> > diff --git a/pypy/objspace/std/test/test_unicodeobject.py
> b/pypy/objspace/std/test/test_unicodeobject.py
> > --- a/pypy/objspace/std/test/test_unicodeobject.py
> > +++ b/pypy/objspace/std/test/test_unicodeobject.py
> > @@ -217,7 +217,7 @@
> >          # check that titlecased chars are lowered correctly
> >          # \u1ffc is the titlecased char
> >          assert ('\u1ff3\u1ff3\u1ffc\u1ffc'.capitalize() ==
> > -                '\u1ffc\u1ff3\u1ff3\u1ff3')
> > +                '\u03a9\u0399\u1ff3\u1ff3\u1ff3')
> >          # check with cased non-letter chars
> >          assert ('\u24c5\u24ce\u24c9\u24bd\u24c4\u24c3'.capitalize() ==
> >                  '\u24c5\u24e8\u24e3\u24d7\u24de\u24dd')
> > diff --git a/pypy/objspace/std/unicodeobject.py
> b/pypy/objspace/std/unicodeobject.py
> > --- a/pypy/objspace/std/unicodeobject.py
> > +++ b/pypy/objspace/std/unicodeobject.py
> > @@ -155,13 +155,16 @@
> >          return unicodedb.islinebreak(ord(ch))
> >
> >      def _upper(self, ch):
> > -        return unichr(unicodedb.toupper(ord(ch)))
> > +        return u''.join([unichr(x) for x in
> > +                         unicodedb.toupper_full(ord(ch))])
> >
> >      def _lower(self, ch):
> > -        return unichr(unicodedb.tolower(ord(ch)))
> > +        return u''.join([unichr(x) for x in
> > +                         unicodedb.tolower_full(ord(ch))])
> >
> >      def _title(self, ch):
> > -        return unichr(unicodedb.totitle(ord(ch)))
> > +        return u''.join([unichr(x) for x in
> > +                         unicodedb.totitle_full(ord(ch))])
> >
> >      def _newlist_unwrapped(self, space, lst):
> >          return space.newlist_unicode(lst)
> > _______________________________________________
> > pypy-commit mailing list
> > pypy-commit at python.org
> > https://mail.python.org/mailman/listinfo/pypy-commit
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>



-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160201/82b639b7/attachment.html>

From fijall at gmail.com  Mon Feb  1 14:57:23 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Mon, 1 Feb 2016 20:57:23 +0100
Subject: [pypy-dev] [pypy-commit] pypy py3.3: Fix unicode.capitalize()
 test to pass with CPython3.3, 
In-Reply-To: <CAGmFidZ_j+XyagqONPduwYF18zANtW_f_ZCOg=4Sf8M9Mj89JA@mail.gmail.com>
References: <56ae9bdc.a3abc20a.ddb4.ffff9400@mx.google.com>
 <CAK5idxQNGTPzLZdzf563tgz=4Z1=5qrp0wGbfuaGo4B50BKRkw@mail.gmail.com>
 <CAGmFidZ_j+XyagqONPduwYF18zANtW_f_ZCOg=4Sf8M9Mj89JA@mail.gmail.com>
Message-ID: <CAK5idxQFOixVzQsyaFBdcifaQ2k-=S82=TeGRSGfW2VFBPisDg@mail.gmail.com>

The problem is usually that "performance later" is never done because
noone looks at those places

On Mon, Feb 1, 2016 at 11:06 AM, Amaury Forgeot d'Arc
<amauryfa at gmail.com> wrote:
> 2016-02-01 9:59 GMT+01:00 Maciej Fijalkowski <fijall at gmail.com>:
>>
>> Those things are probably why pypy3 is so much slower than pypy2
>
>
> Agreed. I prefer to have things correct first, and work on performance
> later.
> For this particular case though, do you have an idea on how to improve this?
> Pass the UnicodeBuilder to unicodedb.toupper_full()?
>
>>
>>
>> On Mon, Feb 1, 2016 at 12:42 AM, amauryfa <pypy.commits at gmail.com> wrote:
>> > Author: Amaury Forgeot d'Arc <amauryfa at gmail.com>
>> > Branch: py3.3
>> > Changeset: r82021:44aa48e4d16a
>> > Date: 2016-02-01 00:31 +0100
>> > http://bitbucket.org/pypy/pypy/changeset/44aa48e4d16a/
>> >
>> > Log:    Fix unicode.capitalize() test to pass with CPython3.3, and
>> > implement
>> >         it for PyPy. Probably not the fastest implementation...
>> >
>> > diff --git a/pypy/objspace/std/test/test_unicodeobject.py
>> > b/pypy/objspace/std/test/test_unicodeobject.py
>> > --- a/pypy/objspace/std/test/test_unicodeobject.py
>> > +++ b/pypy/objspace/std/test/test_unicodeobject.py
>> > @@ -217,7 +217,7 @@
>> >          # check that titlecased chars are lowered correctly
>> >          # \u1ffc is the titlecased char
>> >          assert ('\u1ff3\u1ff3\u1ffc\u1ffc'.capitalize() ==
>> > -                '\u1ffc\u1ff3\u1ff3\u1ff3')
>> > +                '\u03a9\u0399\u1ff3\u1ff3\u1ff3')
>> >          # check with cased non-letter chars
>> >          assert ('\u24c5\u24ce\u24c9\u24bd\u24c4\u24c3'.capitalize() ==
>> >                  '\u24c5\u24e8\u24e3\u24d7\u24de\u24dd')
>> > diff --git a/pypy/objspace/std/unicodeobject.py
>> > b/pypy/objspace/std/unicodeobject.py
>> > --- a/pypy/objspace/std/unicodeobject.py
>> > +++ b/pypy/objspace/std/unicodeobject.py
>> > @@ -155,13 +155,16 @@
>> >          return unicodedb.islinebreak(ord(ch))
>> >
>> >      def _upper(self, ch):
>> > -        return unichr(unicodedb.toupper(ord(ch)))
>> > +        return u''.join([unichr(x) for x in
>> > +                         unicodedb.toupper_full(ord(ch))])
>> >
>> >      def _lower(self, ch):
>> > -        return unichr(unicodedb.tolower(ord(ch)))
>> > +        return u''.join([unichr(x) for x in
>> > +                         unicodedb.tolower_full(ord(ch))])
>> >
>> >      def _title(self, ch):
>> > -        return unichr(unicodedb.totitle(ord(ch)))
>> > +        return u''.join([unichr(x) for x in
>> > +                         unicodedb.totitle_full(ord(ch))])
>> >
>> >      def _newlist_unwrapped(self, space, lst):
>> >          return space.newlist_unicode(lst)
>> > _______________________________________________
>> > pypy-commit mailing list
>> > pypy-commit at python.org
>> > https://mail.python.org/mailman/listinfo/pypy-commit
>> _______________________________________________
>> pypy-dev mailing list
>> pypy-dev at python.org
>> https://mail.python.org/mailman/listinfo/pypy-dev
>
>
>
>
> --
> Amaury Forgeot d'Arc

From cfbolz at gmx.de  Tue Feb  2 07:11:00 2016
From: cfbolz at gmx.de (Carl Friedrich Bolz)
Date: Tue, 2 Feb 2016 13:11:00 +0100
Subject: [pypy-dev] Call for Participation: Virtual Machine Summer School
 2016
Message-ID: <56B09CD4.8060803@gmx.de>

Call for Participation

Virtual Machines Summer School 2016 (#vmss16)
May 31 - June 3 2016
Cumberland Lodge, UK
http://soft-dev.org/events/vmss16/

Early Bird Registration Period: January 11 - February 15, 2016
Regular Registration Period: February 16 - April 30, 2016


The Virtual Machines Summer School (VMSS) will take place in
Cumberland Lodge, UK in summer 2016 just outside London. The aim of
the summer school is to give early career researchers (PhD students
and postdocs particularly) an overview of the field, and to meet some
of its top thinkers.

Venue: Cumberland Lodge is a former royal hunting lodge in Windsor
Great Park, a few miles south of Windsor castle. Since all
participants will be staying at the Lodge, a concentrated and
inspiring atmosphere is guaranteed.

Registration is subsidised by the EPRSC, so costs are low,
particularly for those who register early. There are travel grants
available for students that might otherwise be unable to attend the
summer school.

For further information and registration please visit:
http://soft-dev.org/events/vmss16/


Confirmed Speakers:

Antony Hosking (Purdue University)
Ben Titzer (Google)
Carl Friedrich Bolz (King's College London)
Chris Seaton (Oracle Labs)
Cliff Click (H2O)
Edd Barrett (King's College London)
Gilles Duboscq (Oracle Labs)
Jennifer Sartor (Vrije Universiteit Brussel)
Mario Wolczko (Oracle Labs)
Paul Tarau (University of North Texas)
Richard Jones (University of Kent)
Steve Blackburn (Australian National University)
Vyacheslav Egorov (Google)


Organizers:

Laurence Tratt & Carl Friedrich Bolz (King's College London)

From planrichi at gmail.com  Tue Feb  2 12:11:50 2016
From: planrichi at gmail.com (Richard Plangger)
Date: Tue, 2 Feb 2016 18:11:50 +0100
Subject: [pypy-dev] s390x backend gil and threading issue
Message-ID: <56B0E356.9020006@gmail.com>

hi,

I'm currently searching for a problem, I have debugged for quite a long
time. I think this is the root problem why the pypy translation with
pypy is still slower than cpython. Here are some of my findings
(+questions):

The list of last tests that fail all have one thing in common: They have
an issue with the gil/threading. (See [1])
Most interesting ones are the last five.

* test_gc_locking (2x) fail on the build bot (only using cpython), but
not on my machine. This is strange because bbot and my vm use the same
distro, same compiler version, .... the only difference is that bbot has
better hardware and the tests are run with testrunner.
Is there another way I can reproduce this?

* test_ping_pong. (-A test) ping pong from one thread to another
stressing locking and the GIL switch. On s390x and the translated VM
this takes really long (10 seconds and on bbot it seems to exceed 30
seconds when run in parallel). However if I run the same test with
PYPYLOG=jit:- it completes in ~0.96 seconds (in gdb it is the same). If
you subtract the time needed for printing you might end up with the same
speed as x86 has for this test.
What does the printing/gdbing trigger to let the GIL switch happen that
smoothly?

* I have placed memory fences at the same positions as on ppc (2x isync
and lwsync). Are there any other places that need to complete all
pending the memory operations?

* There is one path in call_release_gil (just after the call) where
rpy_fastgil was acquired (because it as 0) and the shadowstack is not
the one of the current thread. Then *rpy_fastgil = 0 is set for the
slowpath function.
Wouldn't it be possible to steal the gil at this point? Would that lead
to a problem?

Cheers,
Richard

[1] http://buildbot.pypy.org/summary?builder=own-linux-s390x

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160202/c039d382/attachment.sig>

From n210241048576 at gmail.com  Sat Feb  6 23:55:40 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Sat, 6 Feb 2016 20:55:40 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
Message-ID: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>

I am trying to update Pypy. I want to build Pypy from source using the
instructions at http://doc.pypy.org/en/latest/build.html in order to get
the latest bugfixes and improvements.

However, all of the last 5 nightly builds shown at
http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their tests. So
I can't tell what a good revision to update to is.

What is the last good revision of Pypy?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160206/92567426/attachment.html>

From matti.picus at gmail.com  Sun Feb  7 12:05:19 2016
From: matti.picus at gmail.com (Matti Picus)
Date: Sun, 7 Feb 2016 19:05:19 +0200
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
Message-ID: <56B7794F.4080101@gmail.com>


On 07/02/16 06:55, Robert Grosse wrote:
> I am trying to update Pypy. I want to build Pypy from source using the 
> instructions at http://doc.pypy.org/en/latest/build.html in order to 
> get the latest bugfixes and improvements.
>
> However, all of the last 5 nightly builds shown at 
> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their 
> tests. So I can't tell what a good revision to update to is.
>
> What is the last good revision of Pypy?
>
The builds have been failing "only" for vmprof tests, everything else 
should work.
Matti

From n210241048576 at gmail.com  Sun Feb  7 16:26:58 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Sun, 7 Feb 2016 13:26:58 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <56B7794F.4080101@gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
Message-ID: <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>

I updated Pypy, but I'm still getting random segfaults. Is there any way to
see what the problem might be? It just says segfault, so there's no
information. Also, the same code works in CPython.

2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:

>
> On 07/02/16 06:55, Robert Grosse wrote:
>
>> I am trying to update Pypy. I want to build Pypy from source using the
>> instructions at http://doc.pypy.org/en/latest/build.html in order to get
>> the latest bugfixes and improvements.
>>
>> However, all of the last 5 nightly builds shown at
>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their tests.
>> So I can't tell what a good revision to update to is.
>>
>> What is the last good revision of Pypy?
>>
>> The builds have been failing "only" for vmprof tests, everything else
> should work.
> Matti
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160207/1b73cbba/attachment.html>

From fijall at gmail.com  Mon Feb  8 03:51:53 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Mon, 8 Feb 2016 09:51:53 +0100
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
Message-ID: <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>

Hi Robert

You need to explain in details what are you doing and how can we reproduce it

On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <n210241048576 at gmail.com> wrote:
> I updated Pypy, but I'm still getting random segfaults. Is there any way to
> see what the problem might be? It just says segfault, so there's no
> information. Also, the same code works in CPython.
>
> 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
>>
>>
>> On 07/02/16 06:55, Robert Grosse wrote:
>>>
>>> I am trying to update Pypy. I want to build Pypy from source using the
>>> instructions at http://doc.pypy.org/en/latest/build.html in order to get the
>>> latest bugfixes and improvements.
>>>
>>> However, all of the last 5 nightly builds shown at
>>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their tests. So I
>>> can't tell what a good revision to update to is.
>>>
>>> What is the last good revision of Pypy?
>>>
>> The builds have been failing "only" for vmprof tests, everything else
>> should work.
>> Matti
>
>
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>

From m at magnusmorton.com  Mon Feb  8 18:01:26 2016
From: m at magnusmorton.com (Magnus Morton)
Date: Mon, 8 Feb 2016 23:01:26 +0000
Subject: [pypy-dev] Question about "__extend__" hacks (in pypyjit module)
Message-ID: <CAFF308C-D70F-496F-9F62-129160CE604E@magnusmorton.com>

Hi,

In the __init__.py for the ?pypyjit? module there?s a comment in the ?setup_after_space_initialization? method "force the __extend__ hacks to occur early? (line 34) followed by two imports. What are these __extend__ hacks?

Many thanks,
Magnus 


From fijall at gmail.com  Mon Feb  8 18:24:37 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Tue, 9 Feb 2016 00:24:37 +0100
Subject: [pypy-dev] Question about "__extend__" hacks (in pypyjit module)
In-Reply-To: <CAFF308C-D70F-496F-9F62-129160CE604E@magnusmorton.com>
References: <CAFF308C-D70F-496F-9F62-129160CE604E@magnusmorton.com>
Message-ID: <CAK5idxREpwFfjPE_GxYkREVjZVeCCuF0LaGi8Q_V7EP4m0btkQ@mail.gmail.com>

__extend__ hacks add extra methods to classes

On Tue, Feb 9, 2016 at 12:01 AM, Magnus Morton <m at magnusmorton.com> wrote:
> Hi,
>
> In the __init__.py for the ?pypyjit? module there?s a comment in the ?setup_after_space_initialization? method "force the __extend__ hacks to occur early? (line 34) followed by two imports. What are these __extend__ hacks?
>
> Many thanks,
> Magnus
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev

From william.leslie.ttg at gmail.com  Mon Feb  8 19:07:14 2016
From: william.leslie.ttg at gmail.com (William ML Leslie)
Date: Tue, 9 Feb 2016 11:07:14 +1100
Subject: [pypy-dev] Question about "__extend__" hacks (in pypyjit module)
In-Reply-To: <CAK5idxREpwFfjPE_GxYkREVjZVeCCuF0LaGi8Q_V7EP4m0btkQ@mail.gmail.com>
References: <CAFF308C-D70F-496F-9F62-129160CE604E@magnusmorton.com>
 <CAK5idxREpwFfjPE_GxYkREVjZVeCCuF0LaGi8Q_V7EP4m0btkQ@mail.gmail.com>
Message-ID: <CAHgd1hG+T9_f-=8rR7cCnevJXMMG4sRM0vxuAhCPfgDyA-yy8A@mail.gmail.com>

On 9 February 2016 at 10:24, Maciej Fijalkowski <fijall at gmail.com> wrote:
> __extend__ hacks add extra methods to classes

See rpython.tool.pairtype and rpython.tool.test.test_pairtype for more
information on this pattern.

-- 
William Leslie

Notice:
Likely much of this email is, by the nature of copyright, covered
under copyright law.  You absolutely MAY reproduce any part of it in
accordance with the copyright law of the nation you are reading this
in.  Any attempt to DENY YOU THOSE RIGHTS would be illegal without
prior contractual agreement.

From n210241048576 at gmail.com  Tue Feb  9 10:54:37 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Tue, 9 Feb 2016 07:54:37 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
Message-ID: <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>

Pypy segfaults every time I try to decompile an app with Krakatau. The same
code still works on CPython (it's just a lot slower obviously). I'll try to
narrow down the circumstances and come up with better repro instructions
later.

This happened on my build from November too, so it's not a recent
regression. And it happened on multiple computers, although I built Pypy
from source in both cases, so there could be something going wrong there.

2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:

> Hi Robert
>
> You need to explain in details what are you doing and how can we reproduce
> it
>
> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <n210241048576 at gmail.com>
> wrote:
> > I updated Pypy, but I'm still getting random segfaults. Is there any way
> to
> > see what the problem might be? It just says segfault, so there's no
> > information. Also, the same code works in CPython.
> >
> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
> >>
> >>
> >> On 07/02/16 06:55, Robert Grosse wrote:
> >>>
> >>> I am trying to update Pypy. I want to build Pypy from source using the
> >>> instructions at http://doc.pypy.org/en/latest/build.html in order to
> get the
> >>> latest bugfixes and improvements.
> >>>
> >>> However, all of the last 5 nightly builds shown at
> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
> tests. So I
> >>> can't tell what a good revision to update to is.
> >>>
> >>> What is the last good revision of Pypy?
> >>>
> >> The builds have been failing "only" for vmprof tests, everything else
> >> should work.
> >> Matti
> >
> >
> >
> > _______________________________________________
> > pypy-dev mailing list
> > pypy-dev at python.org
> > https://mail.python.org/mailman/listinfo/pypy-dev
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160209/d68bedbf/attachment.html>

From fijall at gmail.com  Tue Feb  9 12:33:25 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Tue, 9 Feb 2016 18:33:25 +0100
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
Message-ID: <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>

ok, I used krakatau in the past and it worked, so you need to be more
specific. Notably give me an example program, how to run it etc. I
need to be able to confirm your steps step by step

On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <n210241048576 at gmail.com> wrote:
> Pypy segfaults every time I try to decompile an app with Krakatau. The same
> code still works on CPython (it's just a lot slower obviously). I'll try to
> narrow down the circumstances and come up with better repro instructions
> later.
>
> This happened on my build from November too, so it's not a recent
> regression. And it happened on multiple computers, although I built Pypy
> from source in both cases, so there could be something going wrong there.
>
> 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>
>> Hi Robert
>>
>> You need to explain in details what are you doing and how can we reproduce
>> it
>>
>> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <n210241048576 at gmail.com>
>> wrote:
>> > I updated Pypy, but I'm still getting random segfaults. Is there any way
>> > to
>> > see what the problem might be? It just says segfault, so there's no
>> > information. Also, the same code works in CPython.
>> >
>> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
>> >>
>> >>
>> >> On 07/02/16 06:55, Robert Grosse wrote:
>> >>>
>> >>> I am trying to update Pypy. I want to build Pypy from source using the
>> >>> instructions at http://doc.pypy.org/en/latest/build.html in order to
>> >>> get the
>> >>> latest bugfixes and improvements.
>> >>>
>> >>> However, all of the last 5 nightly builds shown at
>> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
>> >>> tests. So I
>> >>> can't tell what a good revision to update to is.
>> >>>
>> >>> What is the last good revision of Pypy?
>> >>>
>> >> The builds have been failing "only" for vmprof tests, everything else
>> >> should work.
>> >> Matti
>> >
>> >
>> >
>> > _______________________________________________
>> > pypy-dev mailing list
>> > pypy-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pypy-dev
>> >
>
>

From arigo at tunes.org  Tue Feb  9 12:55:27 2016
From: arigo at tunes.org (Armin Rigo)
Date: Tue, 9 Feb 2016 18:55:27 +0100
Subject: [pypy-dev] s390x backend gil and threading issue
In-Reply-To: <56B0E356.9020006@gmail.com>
References: <56B0E356.9020006@gmail.com>
Message-ID: <CAMSv6X15Ln9zK6i5c_T9-5jDKLhozJj3eyQ9o2EWtHLsDXBgFg@mail.gmail.com>

Hi Richard,

On Tue, Feb 2, 2016 at 6:11 PM, Richard Plangger <planrichi at gmail.com> wrote:
> * There is one path in call_release_gil (just after the call) where
> rpy_fastgil was acquired (because it as 0) and the shadowstack is not
> the one of the current thread. Then *rpy_fastgil = 0 is set for the
> slowpath function.
> Wouldn't it be possible to steal the gil at this point? Would that lead
> to a problem?

No, it's not a problem: setting *rpy_fastgil to zero releases the GIL
again, and it will be re-acquired again by the called function (at
reacqgil_addr).  There is no issue if the GIL is re-acquired by a
different thread exactly here; we will simply block in reacqgil_addr.

Note that we should in theory do a "lwsync" just before setting
*rpy_fastgil to zero, like we do in
call_releasegil_addr_and_move_real_arguments().  It's not done, but I
*think* it doesn't hurt in this particular case.  I may actually be
very wrong, but I base my reasoning on these facts:

1) "*rpy_fastgil=0" can always appear to occur later, from the point
of view of other processors, which is not a problem

2) in this case the "*rpy_fastgil=0" cannot appear to occur too early:
it must appear after the "stdcxx" instruction changed it to 1, and
there is no other store between that "stdcxx" and the following
"*rpy_fastgil=0".  So "lwsync" is not useful here.


A bient?t,

Armin.

From n210241048576 at gmail.com  Tue Feb  9 22:19:10 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Tue, 9 Feb 2016 19:19:10 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
Message-ID: <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>

The segfaults only started last week. I suspect that one of my recent
changes triggers the segfault behavior in Pypy. Can you try with the latest
version of Krakatau? If you still can't reproduce it, I can try to figure
out the steps in more detail.



2016-02-09 9:33 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:

> ok, I used krakatau in the past and it worked, so you need to be more
> specific. Notably give me an example program, how to run it etc. I
> need to be able to confirm your steps step by step
>
> On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <n210241048576 at gmail.com>
> wrote:
> > Pypy segfaults every time I try to decompile an app with Krakatau. The
> same
> > code still works on CPython (it's just a lot slower obviously). I'll try
> to
> > narrow down the circumstances and come up with better repro instructions
> > later.
> >
> > This happened on my build from November too, so it's not a recent
> > regression. And it happened on multiple computers, although I built Pypy
> > from source in both cases, so there could be something going wrong there.
> >
> > 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
> >>
> >> Hi Robert
> >>
> >> You need to explain in details what are you doing and how can we
> reproduce
> >> it
> >>
> >> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <n210241048576 at gmail.com
> >
> >> wrote:
> >> > I updated Pypy, but I'm still getting random segfaults. Is there any
> way
> >> > to
> >> > see what the problem might be? It just says segfault, so there's no
> >> > information. Also, the same code works in CPython.
> >> >
> >> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
> >> >>
> >> >>
> >> >> On 07/02/16 06:55, Robert Grosse wrote:
> >> >>>
> >> >>> I am trying to update Pypy. I want to build Pypy from source using
> the
> >> >>> instructions at http://doc.pypy.org/en/latest/build.html in order
> to
> >> >>> get the
> >> >>> latest bugfixes and improvements.
> >> >>>
> >> >>> However, all of the last 5 nightly builds shown at
> >> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
> >> >>> tests. So I
> >> >>> can't tell what a good revision to update to is.
> >> >>>
> >> >>> What is the last good revision of Pypy?
> >> >>>
> >> >> The builds have been failing "only" for vmprof tests, everything else
> >> >> should work.
> >> >> Matti
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > pypy-dev mailing list
> >> > pypy-dev at python.org
> >> > https://mail.python.org/mailman/listinfo/pypy-dev
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160209/f44d2a8c/attachment.html>

From planrichi at gmail.com  Thu Feb 11 12:17:46 2016
From: planrichi at gmail.com (Richard Plangger)
Date: Thu, 11 Feb 2016 18:17:46 +0100
Subject: [pypy-dev] s390x jit backend the first results and status update
Message-ID: <56BCC23A.9090709@gmail.com>

Hi,

I have been looking quite elaborately to find the last remaining issues
in the JIT backend. I identified some problems (related to the ABI for
floats and ffi issues). Those are fixed.

There are two major left:

1) Bug that occurs very late in the translation of PyPy. As you are
aware I'm not able to reproduce it with the ssh access to my s390x
machine. It looks to me like a double free of a memory chunk, or a
miscalculation that only occurs when a lot of memory is allocated >4GB.
When I can my hands on a 8GB RAM machine I'm sure I can fix it easily.

2) Speed is currently faster than CPython on all benchmarks but probably
not on translation (which I could not run) and bm_mdp.
See here [1]. If you compare it to the results reported by Armin for PPC
& X86 ([2]) then I get around 50%-80% of the speedup.
I have had a look at a lot of profiles (generated with valgrind) but did
not find anything that is too slow. Would there be a difference when I
run the benchmark on real hardware?

Sadly not all tests on build bot are green. The ones that fail, fail
because some thread did not start in time. Or some lock was hold too
long. Eventually these tests will pass, but the suite just stops them. I
cannot reproduce that on my s390x VM either, because it seems this only
occurs under heavy load while running the test suite.

At the end I want to mention that it seems that there is a problem
related to the some special macros expanded by GCC (e.g. WCOREDUMP).
I have reported the problem to the glibc bug tracker [3]. I have fixed
the problem in pypy by altering the type provided to the macro, but
there might be more problems while compiling pypy.

Cheers,
Richard

[1] https://bpaste.net/show/d1af45831627
[2] http://morepypy.blogspot.co.at/2015/10/powerpc-backend-for-jit.html
[3] https://sourceware.org/bugzilla/show_bug.cgi?id=19613

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160211/aafc7575/attachment.sig>

From n210241048576 at gmail.com  Sun Feb 14 17:44:21 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Sun, 14 Feb 2016 14:44:21 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
 <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
Message-ID: <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>

The following steps should let you reproduce it. It segfaults for me every
time. Though interestingly, the actual place it segfaults changes from run
to run.

First checkout Krakatau a43b2e7e0a53bca9fe7c34d97b3b3738d662f8d5 (the
latest)

Then run
pypy Krakatau/decompile.py -out <tempdir> -nauto -skip <path to rt.jar>

where <tempdir> is any writeable directory. For example
pypy Krakatau/decompile.py -out temp -nauto -skip
/usr/lib/jvm/java-8-oracle/jre/lib/rt.jar


Decompiling almost anything segfaults, but this is the simplest setup. Feel
free to respond if you still can't reproduce it.




2016-02-09 19:19 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:

> The segfaults only started last week. I suspect that one of my recent
> changes triggers the segfault behavior in Pypy. Can you try with the latest
> version of Krakatau? If you still can't reproduce it, I can try to figure
> out the steps in more detail.
>
>
>
> 2016-02-09 9:33 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>
>> ok, I used krakatau in the past and it worked, so you need to be more
>> specific. Notably give me an example program, how to run it etc. I
>> need to be able to confirm your steps step by step
>>
>> On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <n210241048576 at gmail.com>
>> wrote:
>> > Pypy segfaults every time I try to decompile an app with Krakatau. The
>> same
>> > code still works on CPython (it's just a lot slower obviously). I'll
>> try to
>> > narrow down the circumstances and come up with better repro instructions
>> > later.
>> >
>> > This happened on my build from November too, so it's not a recent
>> > regression. And it happened on multiple computers, although I built Pypy
>> > from source in both cases, so there could be something going wrong
>> there.
>> >
>> > 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>> >>
>> >> Hi Robert
>> >>
>> >> You need to explain in details what are you doing and how can we
>> reproduce
>> >> it
>> >>
>> >> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <
>> n210241048576 at gmail.com>
>> >> wrote:
>> >> > I updated Pypy, but I'm still getting random segfaults. Is there any
>> way
>> >> > to
>> >> > see what the problem might be? It just says segfault, so there's no
>> >> > information. Also, the same code works in CPython.
>> >> >
>> >> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
>> >> >>
>> >> >>
>> >> >> On 07/02/16 06:55, Robert Grosse wrote:
>> >> >>>
>> >> >>> I am trying to update Pypy. I want to build Pypy from source using
>> the
>> >> >>> instructions at http://doc.pypy.org/en/latest/build.html in order
>> to
>> >> >>> get the
>> >> >>> latest bugfixes and improvements.
>> >> >>>
>> >> >>> However, all of the last 5 nightly builds shown at
>> >> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
>> >> >>> tests. So I
>> >> >>> can't tell what a good revision to update to is.
>> >> >>>
>> >> >>> What is the last good revision of Pypy?
>> >> >>>
>> >> >> The builds have been failing "only" for vmprof tests, everything
>> else
>> >> >> should work.
>> >> >> Matti
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > pypy-dev mailing list
>> >> > pypy-dev at python.org
>> >> > https://mail.python.org/mailman/listinfo/pypy-dev
>> >> >
>> >
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160214/f9abf3da/attachment.html>

From n210241048576 at gmail.com  Sun Feb 14 17:51:25 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Sun, 14 Feb 2016 14:51:25 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
 <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
 <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>
Message-ID: <CALJjGiv=i5mGHtWrx-zL8J=1Kdb=Li5_XHd5RF-Di8o=jqytww@mail.gmail.com>

I tried running pypy under gdb, and it turns out that while it crashes at a
nondeterminstic point in the Python program, the segfault always appears at
the same location in the pypy binary. Here's a backtrace

#0  0x00007ffff58a91f5 in
pypy_g_OptRewrite_replace_guard_class_with_guard_value () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#1  0x00007ffff58a9e8b in pypy_g_OptRewrite_optimize_GUARD_VALUE ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#2  0x00007ffff58d7e75 in pypy_g_dispatch_optimize___star_0_5 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#3  0x00007ffff58a844e in pypy_g_OptRewrite_propagate_forward ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#4  0x00007ffff5889acf in
pypy_g_OptIntBounds__optimize_guard_true_false_value
    () from /home/rsg/Pypy/pypy/built/libpypy-c.so
#5  0x00007ffff58d8ef5 in pypy_g_dispatch_optimize___star_0_6 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#6  0x00007ffff58837d9 in pypy_g_OptIntBounds_propagate_forward ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#7  0x00007ffff58cce8e in pypy_g_UnrollOptimizer_inline_short_preamble ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#8  0x00007ffff58ced40 in pypy_g_UnrollOptimizer_jump_to_existing_trace ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#9  0x00007ffff58d25f9 in pypy_g_UnrollOptimizer_optimize_bridge ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#10 0x00007ffff585fc69 in pypy_g_optimize_trace ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#11 0x00007ffff5817b68 in pypy_g_compile_trace ()
---Type <return> to continue, or q <return> to quit---
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#12 0x00007ffff59d15e4 in pypy_g_MetaInterp_compile_trace ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#13 0x00007ffff59a09cc in pypy_g_MetaInterp_reached_loop_header ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#14 0x00007ffff597858a in pypy_g_MIFrame_opimpl_jit_merge_point ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#15 0x00007ffff59753f6 in pypy_g_handler_jit_merge_point_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#16 0x00007ffff5912c7d in pypy_g_MIFrame_run_one_step ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#17 0x00007ffff5913106 in pypy_g_MetaInterp_interpret ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#18 0x00007ffff59f878e in pypy_g_MetaInterp__handle_guard_failure ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#19 0x00007ffff59ed76a in pypy_g_MetaInterp_handle_guard_failure ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#20 0x00007ffff5813805 in
pypy_g_AbstractResumeGuardDescr__trace_and_compile_from () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#21 0x00007ffff5813c08 in pypy_g_AbstractResumeGuardDescr_handle_fail ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#22 0x00007ffff5aa7313 in pypy_g_execute_assembler.star_2_14 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
---Type <return> to continue, or q <return> to quit---
#23 0x00007ffff5aa7686 in pypy_g_maybe_compile_and_run.star_5_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#24 0x00007ffff5a4024e in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#25 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#26 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#27 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#28 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#29 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#30 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#31 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#32 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#33 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#34 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
---Type <return> to continue, or q <return> to quit---
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#35 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#36 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#37 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#38 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#39 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#40 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#41 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#42 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#43 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#44 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#45 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
---Type <return> to continue, or q <return> to quit---
#46 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#47 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#48 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#49 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#50 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#51 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#52 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#53 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#54 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#55 0x00007ffff4b52ef9 in pypy_g_dispatcher_5 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#56 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#57 0x00007ffff56a9555 in pypy_g_W_TypeObject_descr_call ()
---Type <return> to continue, or q <return> to quit---
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#58 0x00007ffff4b84547 in pypy_g.call_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#59 0x00007ffff4e85d21 in
pypy_g_BuiltinCodePassThroughArguments1_funcrun_obj
    () from /home/rsg/Pypy/pypy/built/libpypy-c.so
#60 0x00007ffff4b52f19 in pypy_g_dispatcher_5 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#61 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#62 0x00007ffff4e5bded in pypy_g_call_valuestack__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#63 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#64 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#65 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#66 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#67 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#68 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
---Type <return> to continue, or q <return> to quit---
#69 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#70 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#71 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#72 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#73 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#74 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#75 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#76 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#77 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#78 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#79 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#80 0x00007ffff54682ce in pypy_g_portal_35 ()
---Type <return> to continue, or q <return> to quit---
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#81 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#82 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#83 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#84 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#85 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#86 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#87 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#88 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#89 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#90 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#91 0x00007ffff54dfe88 in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
---Type <return> to continue, or q <return> to quit---
#92 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#93 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#94 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#95 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#96 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#97 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#98 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#99 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#100 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#101 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#102 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#103 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
---Type <return> to continue, or q <return> to quit---
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#104 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#105 0x00007ffff4eb020e in pypy_g_EXEC_STMT__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#106 0x00007ffff4eb5ed6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#107 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#108 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#109 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#110 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#111 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#112 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#113 0x00007ffff4eb73c4 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#114 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
---Type <return> to continue, or q <return> to quit---
#115 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#116 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#117 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#118 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#119 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#120 0x00007ffff4eb72a9 in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#121 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#122 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#123 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#124 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#125 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#126 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
---Type <return> to continue, or q <return> to quit---
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#127 0x00007ffff4eb732d in pypy_g_dispatch_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#128 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#129 0x00007ffff54682ce in pypy_g_portal_35 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#130 0x00007ffff5a40325 in
pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
/home/rsg/Pypy/pypy/built/libpypy-c.so
#131 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#132 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#133 0x00007ffff4e45dfe in pypy_g_call_function.star_2 ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#134 0x00007ffff4d9907e in pypy_g_entry_point ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#135 0x00007ffff5e1a055 in pypy_main_function ()
   from /home/rsg/Pypy/pypy/built/libpypy-c.so
#136 0x00007ffff2decec5 in __libc_start_main ()
   from /lib/x86_64-linux-gnu/libc.so.6
#137 0x00000000004005fe in _start ()



2016-02-14 14:44 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:

> The following steps should let you reproduce it. It segfaults for me every
> time. Though interestingly, the actual place it segfaults changes from run
> to run.
>
> First checkout Krakatau a43b2e7e0a53bca9fe7c34d97b3b3738d662f8d5 (the
> latest)
>
> Then run
> pypy Krakatau/decompile.py -out <tempdir> -nauto -skip <path to rt.jar>
>
> where <tempdir> is any writeable directory. For example
> pypy Krakatau/decompile.py -out temp -nauto -skip
> /usr/lib/jvm/java-8-oracle/jre/lib/rt.jar
>
>
> Decompiling almost anything segfaults, but this is the simplest setup.
> Feel free to respond if you still can't reproduce it.
>
>
>
>
> 2016-02-09 19:19 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
>
>> The segfaults only started last week. I suspect that one of my recent
>> changes triggers the segfault behavior in Pypy. Can you try with the latest
>> version of Krakatau? If you still can't reproduce it, I can try to figure
>> out the steps in more detail.
>>
>>
>>
>> 2016-02-09 9:33 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>
>>> ok, I used krakatau in the past and it worked, so you need to be more
>>> specific. Notably give me an example program, how to run it etc. I
>>> need to be able to confirm your steps step by step
>>>
>>> On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <n210241048576 at gmail.com>
>>> wrote:
>>> > Pypy segfaults every time I try to decompile an app with Krakatau. The
>>> same
>>> > code still works on CPython (it's just a lot slower obviously). I'll
>>> try to
>>> > narrow down the circumstances and come up with better repro
>>> instructions
>>> > later.
>>> >
>>> > This happened on my build from November too, so it's not a recent
>>> > regression. And it happened on multiple computers, although I built
>>> Pypy
>>> > from source in both cases, so there could be something going wrong
>>> there.
>>> >
>>> > 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>> >>
>>> >> Hi Robert
>>> >>
>>> >> You need to explain in details what are you doing and how can we
>>> reproduce
>>> >> it
>>> >>
>>> >> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <
>>> n210241048576 at gmail.com>
>>> >> wrote:
>>> >> > I updated Pypy, but I'm still getting random segfaults. Is there
>>> any way
>>> >> > to
>>> >> > see what the problem might be? It just says segfault, so there's no
>>> >> > information. Also, the same code works in CPython.
>>> >> >
>>> >> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
>>> >> >>
>>> >> >>
>>> >> >> On 07/02/16 06:55, Robert Grosse wrote:
>>> >> >>>
>>> >> >>> I am trying to update Pypy. I want to build Pypy from source
>>> using the
>>> >> >>> instructions at http://doc.pypy.org/en/latest/build.html in
>>> order to
>>> >> >>> get the
>>> >> >>> latest bugfixes and improvements.
>>> >> >>>
>>> >> >>> However, all of the last 5 nightly builds shown at
>>> >> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
>>> >> >>> tests. So I
>>> >> >>> can't tell what a good revision to update to is.
>>> >> >>>
>>> >> >>> What is the last good revision of Pypy?
>>> >> >>>
>>> >> >> The builds have been failing "only" for vmprof tests, everything
>>> else
>>> >> >> should work.
>>> >> >> Matti
>>> >> >
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > pypy-dev mailing list
>>> >> > pypy-dev at python.org
>>> >> > https://mail.python.org/mailman/listinfo/pypy-dev
>>> >> >
>>> >
>>> >
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160214/2ad6332c/attachment-0001.html>

From n210241048576 at gmail.com  Sun Feb 14 19:02:29 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Sun, 14 Feb 2016 16:02:29 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGiv=i5mGHtWrx-zL8J=1Kdb=Li5_XHd5RF-Di8o=jqytww@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
 <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
 <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>
 <CALJjGiv=i5mGHtWrx-zL8J=1Kdb=Li5_XHd5RF-Di8o=jqytww@mail.gmail.com>
Message-ID: <CALJjGis8_G+7tDr5BYeA_HpXGA7ubAduMjOrJENxL1pFHLHb4Q@mail.gmail.com>

I created a self contained repro script that doesn't require you to have
Java installed or any temp directories.

To run, just checkout branch pypy_bug in Krakatau
(0d739be3707d3b3210fc1b2894a9e7b47334d215)
and run
pypy Krakatau/decompile.py -nauto -out temp -r -path
Krakatau/tests/classes/ Krakatau/tests/classes/



2016-02-14 14:51 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:

> I tried running pypy under gdb, and it turns out that while it crashes at
> a nondeterminstic point in the Python program, the segfault always appears
> at the same location in the pypy binary. Here's a backtrace
>
> #0  0x00007ffff58a91f5 in
> pypy_g_OptRewrite_replace_guard_class_with_guard_value () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #1  0x00007ffff58a9e8b in pypy_g_OptRewrite_optimize_GUARD_VALUE ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #2  0x00007ffff58d7e75 in pypy_g_dispatch_optimize___star_0_5 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #3  0x00007ffff58a844e in pypy_g_OptRewrite_propagate_forward ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #4  0x00007ffff5889acf in
> pypy_g_OptIntBounds__optimize_guard_true_false_value
>     () from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #5  0x00007ffff58d8ef5 in pypy_g_dispatch_optimize___star_0_6 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #6  0x00007ffff58837d9 in pypy_g_OptIntBounds_propagate_forward ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #7  0x00007ffff58cce8e in pypy_g_UnrollOptimizer_inline_short_preamble ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #8  0x00007ffff58ced40 in pypy_g_UnrollOptimizer_jump_to_existing_trace ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #9  0x00007ffff58d25f9 in pypy_g_UnrollOptimizer_optimize_bridge ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #10 0x00007ffff585fc69 in pypy_g_optimize_trace ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #11 0x00007ffff5817b68 in pypy_g_compile_trace ()
> ---Type <return> to continue, or q <return> to quit---
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #12 0x00007ffff59d15e4 in pypy_g_MetaInterp_compile_trace ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #13 0x00007ffff59a09cc in pypy_g_MetaInterp_reached_loop_header ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #14 0x00007ffff597858a in pypy_g_MIFrame_opimpl_jit_merge_point ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #15 0x00007ffff59753f6 in pypy_g_handler_jit_merge_point_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #16 0x00007ffff5912c7d in pypy_g_MIFrame_run_one_step ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #17 0x00007ffff5913106 in pypy_g_MetaInterp_interpret ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #18 0x00007ffff59f878e in pypy_g_MetaInterp__handle_guard_failure ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #19 0x00007ffff59ed76a in pypy_g_MetaInterp_handle_guard_failure ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #20 0x00007ffff5813805 in
> pypy_g_AbstractResumeGuardDescr__trace_and_compile_from () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #21 0x00007ffff5813c08 in pypy_g_AbstractResumeGuardDescr_handle_fail ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #22 0x00007ffff5aa7313 in pypy_g_execute_assembler.star_2_14 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> ---Type <return> to continue, or q <return> to quit---
> #23 0x00007ffff5aa7686 in pypy_g_maybe_compile_and_run.star_5_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #24 0x00007ffff5a4024e in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #25 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #26 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #27 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #28 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #29 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #30 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #31 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #32 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #33 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #34 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> ---Type <return> to continue, or q <return> to quit---
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #35 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #36 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #37 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #38 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #39 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #40 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #41 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #42 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #43 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #44 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #45 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> ---Type <return> to continue, or q <return> to quit---
> #46 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #47 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #48 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #49 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #50 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #51 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #52 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #53 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #54 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #55 0x00007ffff4b52ef9 in pypy_g_dispatcher_5 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #56 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #57 0x00007ffff56a9555 in pypy_g_W_TypeObject_descr_call ()
> ---Type <return> to continue, or q <return> to quit---
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #58 0x00007ffff4b84547 in pypy_g.call_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #59 0x00007ffff4e85d21 in
> pypy_g_BuiltinCodePassThroughArguments1_funcrun_obj
>     () from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #60 0x00007ffff4b52f19 in pypy_g_dispatcher_5 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #61 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #62 0x00007ffff4e5bded in pypy_g_call_valuestack__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #63 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #64 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #65 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #66 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #67 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #68 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> ---Type <return> to continue, or q <return> to quit---
> #69 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #70 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #71 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #72 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #73 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #74 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #75 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #76 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #77 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #78 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #79 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #80 0x00007ffff54682ce in pypy_g_portal_35 ()
> ---Type <return> to continue, or q <return> to quit---
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #81 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #82 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #83 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #84 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #85 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #86 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #87 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #88 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #89 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #90 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #91 0x00007ffff54dfe88 in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> ---Type <return> to continue, or q <return> to quit---
> #92 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #93 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #94 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #95 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #96 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #97 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #98 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #99 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #100 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #101 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #102 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #103 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> ---Type <return> to continue, or q <return> to quit---
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #104 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #105 0x00007ffff4eb020e in pypy_g_EXEC_STMT__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #106 0x00007ffff4eb5ed6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #107 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #108 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #109 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #110 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #111 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #112 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #113 0x00007ffff4eb73c4 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #114 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> ---Type <return> to continue, or q <return> to quit---
> #115 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #116 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #117 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #118 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #119 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #120 0x00007ffff4eb72a9 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #121 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #122 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #123 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #124 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #125 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #126 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
> ---Type <return> to continue, or q <return> to quit---
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #127 0x00007ffff4eb732d in pypy_g_dispatch_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #128 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #129 0x00007ffff54682ce in pypy_g_portal_35 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #130 0x00007ffff5a40325 in
> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> /home/rsg/Pypy/pypy/built/libpypy-c.so
> #131 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #132 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #133 0x00007ffff4e45dfe in pypy_g_call_function.star_2 ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #134 0x00007ffff4d9907e in pypy_g_entry_point ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #135 0x00007ffff5e1a055 in pypy_main_function ()
>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> #136 0x00007ffff2decec5 in __libc_start_main ()
>    from /lib/x86_64-linux-gnu/libc.so.6
> #137 0x00000000004005fe in _start ()
>
>
>
> 2016-02-14 14:44 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
>
>> The following steps should let you reproduce it. It segfaults for me
>> every time. Though interestingly, the actual place it segfaults changes
>> from run to run.
>>
>> First checkout Krakatau a43b2e7e0a53bca9fe7c34d97b3b3738d662f8d5 (the
>> latest)
>>
>> Then run
>> pypy Krakatau/decompile.py -out <tempdir> -nauto -skip <path to rt.jar>
>>
>> where <tempdir> is any writeable directory. For example
>> pypy Krakatau/decompile.py -out temp -nauto -skip
>> /usr/lib/jvm/java-8-oracle/jre/lib/rt.jar
>>
>>
>> Decompiling almost anything segfaults, but this is the simplest setup.
>> Feel free to respond if you still can't reproduce it.
>>
>>
>>
>>
>> 2016-02-09 19:19 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
>>
>>> The segfaults only started last week. I suspect that one of my recent
>>> changes triggers the segfault behavior in Pypy. Can you try with the latest
>>> version of Krakatau? If you still can't reproduce it, I can try to figure
>>> out the steps in more detail.
>>>
>>>
>>>
>>> 2016-02-09 9:33 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>>
>>>> ok, I used krakatau in the past and it worked, so you need to be more
>>>> specific. Notably give me an example program, how to run it etc. I
>>>> need to be able to confirm your steps step by step
>>>>
>>>> On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <n210241048576 at gmail.com>
>>>> wrote:
>>>> > Pypy segfaults every time I try to decompile an app with Krakatau.
>>>> The same
>>>> > code still works on CPython (it's just a lot slower obviously). I'll
>>>> try to
>>>> > narrow down the circumstances and come up with better repro
>>>> instructions
>>>> > later.
>>>> >
>>>> > This happened on my build from November too, so it's not a recent
>>>> > regression. And it happened on multiple computers, although I built
>>>> Pypy
>>>> > from source in both cases, so there could be something going wrong
>>>> there.
>>>> >
>>>> > 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>>> >>
>>>> >> Hi Robert
>>>> >>
>>>> >> You need to explain in details what are you doing and how can we
>>>> reproduce
>>>> >> it
>>>> >>
>>>> >> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse <
>>>> n210241048576 at gmail.com>
>>>> >> wrote:
>>>> >> > I updated Pypy, but I'm still getting random segfaults. Is there
>>>> any way
>>>> >> > to
>>>> >> > see what the problem might be? It just says segfault, so there's no
>>>> >> > information. Also, the same code works in CPython.
>>>> >> >
>>>> >> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
>>>> >> >>
>>>> >> >>
>>>> >> >> On 07/02/16 06:55, Robert Grosse wrote:
>>>> >> >>>
>>>> >> >>> I am trying to update Pypy. I want to build Pypy from source
>>>> using the
>>>> >> >>> instructions at http://doc.pypy.org/en/latest/build.html in
>>>> order to
>>>> >> >>> get the
>>>> >> >>> latest bugfixes and improvements.
>>>> >> >>>
>>>> >> >>> However, all of the last 5 nightly builds shown at
>>>> >> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
>>>> >> >>> tests. So I
>>>> >> >>> can't tell what a good revision to update to is.
>>>> >> >>>
>>>> >> >>> What is the last good revision of Pypy?
>>>> >> >>>
>>>> >> >> The builds have been failing "only" for vmprof tests, everything
>>>> else
>>>> >> >> should work.
>>>> >> >> Matti
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > pypy-dev mailing list
>>>> >> > pypy-dev at python.org
>>>> >> > https://mail.python.org/mailman/listinfo/pypy-dev
>>>> >> >
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160214/700a155c/attachment-0001.html>

From fijall at gmail.com  Mon Feb 15 01:53:40 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Mon, 15 Feb 2016 07:53:40 +0100
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGis8_G+7tDr5BYeA_HpXGA7ubAduMjOrJENxL1pFHLHb4Q@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
 <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
 <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>
 <CALJjGiv=i5mGHtWrx-zL8J=1Kdb=Li5_XHd5RF-Di8o=jqytww@mail.gmail.com>
 <CALJjGis8_G+7tDr5BYeA_HpXGA7ubAduMjOrJENxL1pFHLHb4Q@mail.gmail.com>
Message-ID: <CAK5idxT9ANxyDkZRNukwkEcCtPq+6yqduGbknhVtS9=sfrAaNA@mail.gmail.com>

Hi Robert!

Thanks for the work to help us reproduce it! Can you put it on the
issue tracker? I can't look right now and I'm afraid it might get lost
otherwise (an issue with a link to pypy-dev post is fine even)

On Mon, Feb 15, 2016 at 1:02 AM, Robert Grosse <n210241048576 at gmail.com> wrote:
> I created a self contained repro script that doesn't require you to have
> Java installed or any temp directories.
>
> To run, just checkout branch pypy_bug in Krakatau
> (0d739be3707d3b3210fc1b2894a9e7b47334d215) and run
> pypy Krakatau/decompile.py -nauto -out temp -r -path Krakatau/tests/classes/
> Krakatau/tests/classes/
>
>
>
> 2016-02-14 14:51 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
>>
>> I tried running pypy under gdb, and it turns out that while it crashes at
>> a nondeterminstic point in the Python program, the segfault always appears
>> at the same location in the pypy binary. Here's a backtrace
>>
>> #0  0x00007ffff58a91f5 in
>> pypy_g_OptRewrite_replace_guard_class_with_guard_value () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #1  0x00007ffff58a9e8b in pypy_g_OptRewrite_optimize_GUARD_VALUE ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #2  0x00007ffff58d7e75 in pypy_g_dispatch_optimize___star_0_5 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #3  0x00007ffff58a844e in pypy_g_OptRewrite_propagate_forward ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #4  0x00007ffff5889acf in
>> pypy_g_OptIntBounds__optimize_guard_true_false_value
>>     () from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #5  0x00007ffff58d8ef5 in pypy_g_dispatch_optimize___star_0_6 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #6  0x00007ffff58837d9 in pypy_g_OptIntBounds_propagate_forward ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #7  0x00007ffff58cce8e in pypy_g_UnrollOptimizer_inline_short_preamble ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #8  0x00007ffff58ced40 in pypy_g_UnrollOptimizer_jump_to_existing_trace ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #9  0x00007ffff58d25f9 in pypy_g_UnrollOptimizer_optimize_bridge ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #10 0x00007ffff585fc69 in pypy_g_optimize_trace ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #11 0x00007ffff5817b68 in pypy_g_compile_trace ()
>> ---Type <return> to continue, or q <return> to quit---
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #12 0x00007ffff59d15e4 in pypy_g_MetaInterp_compile_trace ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #13 0x00007ffff59a09cc in pypy_g_MetaInterp_reached_loop_header ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #14 0x00007ffff597858a in pypy_g_MIFrame_opimpl_jit_merge_point ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #15 0x00007ffff59753f6 in pypy_g_handler_jit_merge_point_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #16 0x00007ffff5912c7d in pypy_g_MIFrame_run_one_step ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #17 0x00007ffff5913106 in pypy_g_MetaInterp_interpret ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #18 0x00007ffff59f878e in pypy_g_MetaInterp__handle_guard_failure ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #19 0x00007ffff59ed76a in pypy_g_MetaInterp_handle_guard_failure ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #20 0x00007ffff5813805 in
>> pypy_g_AbstractResumeGuardDescr__trace_and_compile_from () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #21 0x00007ffff5813c08 in pypy_g_AbstractResumeGuardDescr_handle_fail ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #22 0x00007ffff5aa7313 in pypy_g_execute_assembler.star_2_14 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> ---Type <return> to continue, or q <return> to quit---
>> #23 0x00007ffff5aa7686 in pypy_g_maybe_compile_and_run.star_5_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #24 0x00007ffff5a4024e in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #25 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #26 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #27 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #28 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #29 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #30 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #31 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #32 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #33 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #34 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>> ---Type <return> to continue, or q <return> to quit---
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #35 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #36 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #37 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #38 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #39 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #40 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #41 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #42 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #43 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #44 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #45 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> ---Type <return> to continue, or q <return> to quit---
>> #46 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #47 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #48 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #49 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #50 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #51 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #52 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #53 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #54 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #55 0x00007ffff4b52ef9 in pypy_g_dispatcher_5 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #56 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #57 0x00007ffff56a9555 in pypy_g_W_TypeObject_descr_call ()
>> ---Type <return> to continue, or q <return> to quit---
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #58 0x00007ffff4b84547 in pypy_g.call_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #59 0x00007ffff4e85d21 in
>> pypy_g_BuiltinCodePassThroughArguments1_funcrun_obj
>>     () from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #60 0x00007ffff4b52f19 in pypy_g_dispatcher_5 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #61 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #62 0x00007ffff4e5bded in pypy_g_call_valuestack__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #63 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #64 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #65 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #66 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #67 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #68 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> ---Type <return> to continue, or q <return> to quit---
>> #69 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #70 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #71 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #72 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #73 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #74 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #75 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #76 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #77 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #78 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #79 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #80 0x00007ffff54682ce in pypy_g_portal_35 ()
>> ---Type <return> to continue, or q <return> to quit---
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #81 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #82 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #83 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #84 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #85 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #86 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #87 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #88 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #89 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #90 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #91 0x00007ffff54dfe88 in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> ---Type <return> to continue, or q <return> to quit---
>> #92 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #93 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #94 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #95 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #96 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #97 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #98 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #99 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #100 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #101 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #102 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #103 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>> ---Type <return> to continue, or q <return> to quit---
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #104 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #105 0x00007ffff4eb020e in pypy_g_EXEC_STMT__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #106 0x00007ffff4eb5ed6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #107 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #108 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #109 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #110 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #111 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #112 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #113 0x00007ffff4eb73c4 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #114 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> ---Type <return> to continue, or q <return> to quit---
>> #115 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #116 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #117 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #118 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #119 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #120 0x00007ffff4eb72a9 in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #121 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #122 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #123 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #124 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #125 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #126 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
>> ---Type <return> to continue, or q <return> to quit---
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #127 0x00007ffff4eb732d in pypy_g_dispatch_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #128 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #129 0x00007ffff54682ce in pypy_g_portal_35 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #130 0x00007ffff5a40325 in
>> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
>> /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #131 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #132 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #133 0x00007ffff4e45dfe in pypy_g_call_function.star_2 ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #134 0x00007ffff4d9907e in pypy_g_entry_point ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #135 0x00007ffff5e1a055 in pypy_main_function ()
>>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
>> #136 0x00007ffff2decec5 in __libc_start_main ()
>>    from /lib/x86_64-linux-gnu/libc.so.6
>> #137 0x00000000004005fe in _start ()
>>
>>
>>
>> 2016-02-14 14:44 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
>>>
>>> The following steps should let you reproduce it. It segfaults for me
>>> every time. Though interestingly, the actual place it segfaults changes from
>>> run to run.
>>>
>>> First checkout Krakatau a43b2e7e0a53bca9fe7c34d97b3b3738d662f8d5 (the
>>> latest)
>>>
>>> Then run
>>> pypy Krakatau/decompile.py -out <tempdir> -nauto -skip <path to rt.jar>
>>>
>>> where <tempdir> is any writeable directory. For example
>>> pypy Krakatau/decompile.py -out temp -nauto -skip
>>> /usr/lib/jvm/java-8-oracle/jre/lib/rt.jar
>>>
>>>
>>> Decompiling almost anything segfaults, but this is the simplest setup.
>>> Feel free to respond if you still can't reproduce it.
>>>
>>>
>>>
>>>
>>> 2016-02-09 19:19 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
>>>>
>>>> The segfaults only started last week. I suspect that one of my recent
>>>> changes triggers the segfault behavior in Pypy. Can you try with the latest
>>>> version of Krakatau? If you still can't reproduce it, I can try to figure
>>>> out the steps in more detail.
>>>>
>>>>
>>>>
>>>> 2016-02-09 9:33 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>>>>
>>>>> ok, I used krakatau in the past and it worked, so you need to be more
>>>>> specific. Notably give me an example program, how to run it etc. I
>>>>> need to be able to confirm your steps step by step
>>>>>
>>>>> On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <n210241048576 at gmail.com>
>>>>> wrote:
>>>>> > Pypy segfaults every time I try to decompile an app with Krakatau.
>>>>> > The same
>>>>> > code still works on CPython (it's just a lot slower obviously). I'll
>>>>> > try to
>>>>> > narrow down the circumstances and come up with better repro
>>>>> > instructions
>>>>> > later.
>>>>> >
>>>>> > This happened on my build from November too, so it's not a recent
>>>>> > regression. And it happened on multiple computers, although I built
>>>>> > Pypy
>>>>> > from source in both cases, so there could be something going wrong
>>>>> > there.
>>>>> >
>>>>> > 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
>>>>> >>
>>>>> >> Hi Robert
>>>>> >>
>>>>> >> You need to explain in details what are you doing and how can we
>>>>> >> reproduce
>>>>> >> it
>>>>> >>
>>>>> >> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse
>>>>> >> <n210241048576 at gmail.com>
>>>>> >> wrote:
>>>>> >> > I updated Pypy, but I'm still getting random segfaults. Is there
>>>>> >> > any way
>>>>> >> > to
>>>>> >> > see what the problem might be? It just says segfault, so there's
>>>>> >> > no
>>>>> >> > information. Also, the same code works in CPython.
>>>>> >> >
>>>>> >> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
>>>>> >> >>
>>>>> >> >>
>>>>> >> >> On 07/02/16 06:55, Robert Grosse wrote:
>>>>> >> >>>
>>>>> >> >>> I am trying to update Pypy. I want to build Pypy from source
>>>>> >> >>> using the
>>>>> >> >>> instructions at http://doc.pypy.org/en/latest/build.html in
>>>>> >> >>> order to
>>>>> >> >>> get the
>>>>> >> >>> latest bugfixes and improvements.
>>>>> >> >>>
>>>>> >> >>> However, all of the last 5 nightly builds shown at
>>>>> >> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed their
>>>>> >> >>> tests. So I
>>>>> >> >>> can't tell what a good revision to update to is.
>>>>> >> >>>
>>>>> >> >>> What is the last good revision of Pypy?
>>>>> >> >>>
>>>>> >> >> The builds have been failing "only" for vmprof tests, everything
>>>>> >> >> else
>>>>> >> >> should work.
>>>>> >> >> Matti
>>>>> >> >
>>>>> >> >
>>>>> >> >
>>>>> >> > _______________________________________________
>>>>> >> > pypy-dev mailing list
>>>>> >> > pypy-dev at python.org
>>>>> >> > https://mail.python.org/mailman/listinfo/pypy-dev
>>>>> >> >
>>>>> >
>>>>> >
>>>>
>>>>
>>>
>>
>

From n210241048576 at gmail.com  Mon Feb 15 10:37:54 2016
From: n210241048576 at gmail.com (Robert Grosse)
Date: Mon, 15 Feb 2016 07:37:54 -0800
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CAK5idxT9ANxyDkZRNukwkEcCtPq+6yqduGbknhVtS9=sfrAaNA@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
 <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
 <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>
 <CALJjGiv=i5mGHtWrx-zL8J=1Kdb=Li5_XHd5RF-Di8o=jqytww@mail.gmail.com>
 <CALJjGis8_G+7tDr5BYeA_HpXGA7ubAduMjOrJENxL1pFHLHb4Q@mail.gmail.com>
 <CAK5idxT9ANxyDkZRNukwkEcCtPq+6yqduGbknhVtS9=sfrAaNA@mail.gmail.com>
Message-ID: <CALJjGitGKKYQKjPDcAHKLTJTW7_GsRqS=w8z04v7VXi=Xo+EwA@mail.gmail.com>

https://bitbucket.org/pypy/pypy/issues/2239/segfault-in

2016-02-14 22:53 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:

> Hi Robert!
>
> Thanks for the work to help us reproduce it! Can you put it on the
> issue tracker? I can't look right now and I'm afraid it might get lost
> otherwise (an issue with a link to pypy-dev post is fine even)
>
> On Mon, Feb 15, 2016 at 1:02 AM, Robert Grosse <n210241048576 at gmail.com>
> wrote:
> > I created a self contained repro script that doesn't require you to have
> > Java installed or any temp directories.
> >
> > To run, just checkout branch pypy_bug in Krakatau
> > (0d739be3707d3b3210fc1b2894a9e7b47334d215) and run
> > pypy Krakatau/decompile.py -nauto -out temp -r -path
> Krakatau/tests/classes/
> > Krakatau/tests/classes/
> >
> >
> >
> > 2016-02-14 14:51 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
> >>
> >> I tried running pypy under gdb, and it turns out that while it crashes
> at
> >> a nondeterminstic point in the Python program, the segfault always
> appears
> >> at the same location in the pypy binary. Here's a backtrace
> >>
> >> #0  0x00007ffff58a91f5 in
> >> pypy_g_OptRewrite_replace_guard_class_with_guard_value () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #1  0x00007ffff58a9e8b in pypy_g_OptRewrite_optimize_GUARD_VALUE ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #2  0x00007ffff58d7e75 in pypy_g_dispatch_optimize___star_0_5 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #3  0x00007ffff58a844e in pypy_g_OptRewrite_propagate_forward ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #4  0x00007ffff5889acf in
> >> pypy_g_OptIntBounds__optimize_guard_true_false_value
> >>     () from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #5  0x00007ffff58d8ef5 in pypy_g_dispatch_optimize___star_0_6 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #6  0x00007ffff58837d9 in pypy_g_OptIntBounds_propagate_forward ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #7  0x00007ffff58cce8e in pypy_g_UnrollOptimizer_inline_short_preamble
> ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #8  0x00007ffff58ced40 in pypy_g_UnrollOptimizer_jump_to_existing_trace
> ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #9  0x00007ffff58d25f9 in pypy_g_UnrollOptimizer_optimize_bridge ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #10 0x00007ffff585fc69 in pypy_g_optimize_trace ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #11 0x00007ffff5817b68 in pypy_g_compile_trace ()
> >> ---Type <return> to continue, or q <return> to quit---
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #12 0x00007ffff59d15e4 in pypy_g_MetaInterp_compile_trace ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #13 0x00007ffff59a09cc in pypy_g_MetaInterp_reached_loop_header ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #14 0x00007ffff597858a in pypy_g_MIFrame_opimpl_jit_merge_point ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #15 0x00007ffff59753f6 in pypy_g_handler_jit_merge_point_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #16 0x00007ffff5912c7d in pypy_g_MIFrame_run_one_step ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #17 0x00007ffff5913106 in pypy_g_MetaInterp_interpret ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #18 0x00007ffff59f878e in pypy_g_MetaInterp__handle_guard_failure ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #19 0x00007ffff59ed76a in pypy_g_MetaInterp_handle_guard_failure ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #20 0x00007ffff5813805 in
> >> pypy_g_AbstractResumeGuardDescr__trace_and_compile_from () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #21 0x00007ffff5813c08 in pypy_g_AbstractResumeGuardDescr_handle_fail ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #22 0x00007ffff5aa7313 in pypy_g_execute_assembler.star_2_14 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> ---Type <return> to continue, or q <return> to quit---
> >> #23 0x00007ffff5aa7686 in pypy_g_maybe_compile_and_run.star_5_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #24 0x00007ffff5a4024e in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #25 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #26 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #27 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #28 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #29 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #30 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #31 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #32 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #33 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #34 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> >> ---Type <return> to continue, or q <return> to quit---
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #35 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #36 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #37 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #38 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #39 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #40 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #41 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #42 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #43 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #44 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #45 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> ---Type <return> to continue, or q <return> to quit---
> >> #46 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #47 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #48 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #49 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #50 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #51 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #52 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #53 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #54 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #55 0x00007ffff4b52ef9 in pypy_g_dispatcher_5 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #56 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #57 0x00007ffff56a9555 in pypy_g_W_TypeObject_descr_call ()
> >> ---Type <return> to continue, or q <return> to quit---
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #58 0x00007ffff4b84547 in pypy_g.call_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #59 0x00007ffff4e85d21 in
> >> pypy_g_BuiltinCodePassThroughArguments1_funcrun_obj
> >>     () from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #60 0x00007ffff4b52f19 in pypy_g_dispatcher_5 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #61 0x00007ffff4e7b7da in pypy_g_Function_call_obj_args ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #62 0x00007ffff4e5bded in pypy_g_call_valuestack__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #63 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #64 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #65 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #66 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #67 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #68 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> ---Type <return> to continue, or q <return> to quit---
> >> #69 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #70 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #71 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #72 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #73 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #74 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #75 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #76 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #77 0x00007ffff54df8be in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #78 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #79 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #80 0x00007ffff54682ce in pypy_g_portal_35 ()
> >> ---Type <return> to continue, or q <return> to quit---
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #81 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #82 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #83 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #84 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #85 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #86 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #87 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #88 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #89 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #90 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #91 0x00007ffff54dfe88 in pypy_g_CALL_METHOD__AccessDirect_star_1 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> ---Type <return> to continue, or q <return> to quit---
> >> #92 0x00007ffff4eb7626 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #93 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #94 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #95 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #96 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #97 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #98 0x00007ffff4eb1d2e in pypy_g_CALL_FUNCTION__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #99 0x00007ffff4eb6ff6 in pypy_g_dispatch_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #100 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #101 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #102 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #103 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >> ---Type <return> to continue, or q <return> to quit---
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #104 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #105 0x00007ffff4eb020e in pypy_g_EXEC_STMT__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #106 0x00007ffff4eb5ed6 in pypy_g_dispatch_bytecode__AccessDirect_None
> ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #107 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #108 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #109 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #110 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #111 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #112 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #113 0x00007ffff4eb73c4 in pypy_g_dispatch_bytecode__AccessDirect_None
> ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #114 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> ---Type <return> to continue, or q <return> to quit---
> >> #115 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #116 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #117 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #118 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #119 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #120 0x00007ffff4eb72a9 in pypy_g_dispatch_bytecode__AccessDirect_None
> ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #121 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #122 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #123 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #124 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #125 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #126 0x00007ffff4eb1973 in pypy_g_call_function__AccessDirect_None ()
> >> ---Type <return> to continue, or q <return> to quit---
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #127 0x00007ffff4eb732d in pypy_g_dispatch_bytecode__AccessDirect_None
> ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #128 0x00007ffff4eba679 in pypy_g_handle_bytecode__AccessDirect_None ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #129 0x00007ffff54682ce in pypy_g_portal_35 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #130 0x00007ffff5a40325 in
> >> pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () from
> >> /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #131 0x00007ffff4e9d7c4 in pypy_g_execute_frame ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #132 0x00007ffff5cf7eb5 in pypy_g_execute_frame_rvmprof.star_3 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #133 0x00007ffff4e45dfe in pypy_g_call_function.star_2 ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #134 0x00007ffff4d9907e in pypy_g_entry_point ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #135 0x00007ffff5e1a055 in pypy_main_function ()
> >>    from /home/rsg/Pypy/pypy/built/libpypy-c.so
> >> #136 0x00007ffff2decec5 in __libc_start_main ()
> >>    from /lib/x86_64-linux-gnu/libc.so.6
> >> #137 0x00000000004005fe in _start ()
> >>
> >>
> >>
> >> 2016-02-14 14:44 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
> >>>
> >>> The following steps should let you reproduce it. It segfaults for me
> >>> every time. Though interestingly, the actual place it segfaults
> changes from
> >>> run to run.
> >>>
> >>> First checkout Krakatau a43b2e7e0a53bca9fe7c34d97b3b3738d662f8d5 (the
> >>> latest)
> >>>
> >>> Then run
> >>> pypy Krakatau/decompile.py -out <tempdir> -nauto -skip <path to rt.jar>
> >>>
> >>> where <tempdir> is any writeable directory. For example
> >>> pypy Krakatau/decompile.py -out temp -nauto -skip
> >>> /usr/lib/jvm/java-8-oracle/jre/lib/rt.jar
> >>>
> >>>
> >>> Decompiling almost anything segfaults, but this is the simplest setup.
> >>> Feel free to respond if you still can't reproduce it.
> >>>
> >>>
> >>>
> >>>
> >>> 2016-02-09 19:19 GMT-08:00 Robert Grosse <n210241048576 at gmail.com>:
> >>>>
> >>>> The segfaults only started last week. I suspect that one of my recent
> >>>> changes triggers the segfault behavior in Pypy. Can you try with the
> latest
> >>>> version of Krakatau? If you still can't reproduce it, I can try to
> figure
> >>>> out the steps in more detail.
> >>>>
> >>>>
> >>>>
> >>>> 2016-02-09 9:33 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
> >>>>>
> >>>>> ok, I used krakatau in the past and it worked, so you need to be more
> >>>>> specific. Notably give me an example program, how to run it etc. I
> >>>>> need to be able to confirm your steps step by step
> >>>>>
> >>>>> On Tue, Feb 9, 2016 at 4:54 PM, Robert Grosse <
> n210241048576 at gmail.com>
> >>>>> wrote:
> >>>>> > Pypy segfaults every time I try to decompile an app with Krakatau.
> >>>>> > The same
> >>>>> > code still works on CPython (it's just a lot slower obviously).
> I'll
> >>>>> > try to
> >>>>> > narrow down the circumstances and come up with better repro
> >>>>> > instructions
> >>>>> > later.
> >>>>> >
> >>>>> > This happened on my build from November too, so it's not a recent
> >>>>> > regression. And it happened on multiple computers, although I built
> >>>>> > Pypy
> >>>>> > from source in both cases, so there could be something going wrong
> >>>>> > there.
> >>>>> >
> >>>>> > 2016-02-08 0:51 GMT-08:00 Maciej Fijalkowski <fijall at gmail.com>:
> >>>>> >>
> >>>>> >> Hi Robert
> >>>>> >>
> >>>>> >> You need to explain in details what are you doing and how can we
> >>>>> >> reproduce
> >>>>> >> it
> >>>>> >>
> >>>>> >> On Sun, Feb 7, 2016 at 10:26 PM, Robert Grosse
> >>>>> >> <n210241048576 at gmail.com>
> >>>>> >> wrote:
> >>>>> >> > I updated Pypy, but I'm still getting random segfaults. Is there
> >>>>> >> > any way
> >>>>> >> > to
> >>>>> >> > see what the problem might be? It just says segfault, so there's
> >>>>> >> > no
> >>>>> >> > information. Also, the same code works in CPython.
> >>>>> >> >
> >>>>> >> > 2016-02-07 9:05 GMT-08:00 Matti Picus <matti.picus at gmail.com>:
> >>>>> >> >>
> >>>>> >> >>
> >>>>> >> >> On 07/02/16 06:55, Robert Grosse wrote:
> >>>>> >> >>>
> >>>>> >> >>> I am trying to update Pypy. I want to build Pypy from source
> >>>>> >> >>> using the
> >>>>> >> >>> instructions at http://doc.pypy.org/en/latest/build.html in
> >>>>> >> >>> order to
> >>>>> >> >>> get the
> >>>>> >> >>> latest bugfixes and improvements.
> >>>>> >> >>>
> >>>>> >> >>> However, all of the last 5 nightly builds shown at
> >>>>> >> >>> http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E failed
> their
> >>>>> >> >>> tests. So I
> >>>>> >> >>> can't tell what a good revision to update to is.
> >>>>> >> >>>
> >>>>> >> >>> What is the last good revision of Pypy?
> >>>>> >> >>>
> >>>>> >> >> The builds have been failing "only" for vmprof tests,
> everything
> >>>>> >> >> else
> >>>>> >> >> should work.
> >>>>> >> >> Matti
> >>>>> >> >
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > _______________________________________________
> >>>>> >> > pypy-dev mailing list
> >>>>> >> > pypy-dev at python.org
> >>>>> >> > https://mail.python.org/mailman/listinfo/pypy-dev
> >>>>> >> >
> >>>>> >
> >>>>> >
> >>>>
> >>>>
> >>>
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160215/6e6d2282/attachment-0001.html>

From arigo at tunes.org  Mon Feb 15 12:27:44 2016
From: arigo at tunes.org (Armin Rigo)
Date: Mon, 15 Feb 2016 18:27:44 +0100
Subject: [pypy-dev] What is the last good build of Pypy?
In-Reply-To: <CALJjGitGKKYQKjPDcAHKLTJTW7_GsRqS=w8z04v7VXi=Xo+EwA@mail.gmail.com>
References: <CALJjGivHS-h5aQSgp9P7LTWqj25X8zWGrp0L92hdQuVs4bLQ2A@mail.gmail.com>
 <56B7794F.4080101@gmail.com>
 <CALJjGivqZvO3BdejY2+RoL6V6Cp+Z+dObr0G0yU+fxk=bynfBw@mail.gmail.com>
 <CAK5idxQsgd9KYKpX349qRyXvbbqtWHLtoiCFFyogrzg77cuhtw@mail.gmail.com>
 <CALJjGivUPnwx3ZiP=ivSq5WMTK7KXtvgVeG-+cs-p5x+xULtPw@mail.gmail.com>
 <CAK5idxR6qeon-4S66DCu7=QnpvbRsx8K5oyohajbSU_-Fi_2LQ@mail.gmail.com>
 <CALJjGisxMRfo742Z8TPCB5Ou+mtDDzXAtu7aYqGK1kxOFNFeQA@mail.gmail.com>
 <CALJjGitENuUL7CGwn=C9MxhP2tVBrmPNsJ4gg=MK-F0_x5ja7w@mail.gmail.com>
 <CALJjGiv=i5mGHtWrx-zL8J=1Kdb=Li5_XHd5RF-Di8o=jqytww@mail.gmail.com>
 <CALJjGis8_G+7tDr5BYeA_HpXGA7ubAduMjOrJENxL1pFHLHb4Q@mail.gmail.com>
 <CAK5idxT9ANxyDkZRNukwkEcCtPq+6yqduGbknhVtS9=sfrAaNA@mail.gmail.com>
 <CALJjGitGKKYQKjPDcAHKLTJTW7_GsRqS=w8z04v7VXi=Xo+EwA@mail.gmail.com>
Message-ID: <CAMSv6X3dTqxX7t1hF6SAy_kvOp7cZ=_gpHE7FkZY20Kxd=1xpQ@mail.gmail.com>

Hi Robert,

On Mon, Feb 15, 2016 at 4:37 PM, Robert Grosse <n210241048576 at gmail.com> wrote:
> https://bitbucket.org/pypy/pypy/issues/2239/segfault-in

Thanks!  Your example turned an impossible-to-debug problem into a
relatively easy one.  Fixed and tested in 96c2ec82f010.  Now at least
the command line you give in the issue report completes without a
segfault.


A bient?t,

Armin.

From arigo at tunes.org  Tue Feb 16 08:35:10 2016
From: arigo at tunes.org (Armin Rigo)
Date: Tue, 16 Feb 2016 14:35:10 +0100
Subject: [pypy-dev] Leysin Sprint: instructions
Message-ID: <CAMSv6X3rbjEpU+-iwP=KB+QNuKWBRzaPGNi0cEvEapTPdwTD7w@mail.gmail.com>

Hi all,

If you're coming to the Leysin sprint, a few extra instructions:

* look up your way on
https://www.openstreetmap.org/#map=17/46.34727/7.01722 .  Chalet
Ermina is "up right" in this view.  Scroll a bit left-down to see the
train stations.  The closest is Leysin-Feydey, though you may also go
down in Versmont if you prefer less steep streets.  It's around 10-15
minutes to walk.  There is also a free bus touring the village hourly.

* if you were there in previous years: the Chalet to go to is the
"bottom" one.  Go past the "top" one for 100m more, then back to the
right 100m.

* if you arrive Saturday before 5pm, meet me at L'Essentiel, a new
restaurant nearby.  If you arrive afterwards, go to the Chalet
directly.

* L'Essentiel is in the same place as an old restaurant which I'll not
name here: google maps is not up-to-date, so it has only the old
restaurant --- but it is misplaced...


A bient?t,

Armin.

From fijall at gmail.com  Tue Feb 16 08:53:05 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Tue, 16 Feb 2016 14:53:05 +0100
Subject: [pypy-dev] Leysin Sprint: instructions
In-Reply-To: <CAMSv6X3rbjEpU+-iwP=KB+QNuKWBRzaPGNi0cEvEapTPdwTD7w@mail.gmail.com>
References: <CAMSv6X3rbjEpU+-iwP=KB+QNuKWBRzaPGNi0cEvEapTPdwTD7w@mail.gmail.com>
Message-ID: <CAK5idxQJkiC9itLjf2J2Xb8VTgMMkCbzuRcgZtV8QMXuk2jtFw@mail.gmail.com>

Armin, is L'essentiel on open street map at the right spot?

On Tue, Feb 16, 2016 at 2:35 PM, Armin Rigo <arigo at tunes.org> wrote:
> Hi all,
>
> If you're coming to the Leysin sprint, a few extra instructions:
>
> * look up your way on
> https://www.openstreetmap.org/#map=17/46.34727/7.01722 .  Chalet
> Ermina is "up right" in this view.  Scroll a bit left-down to see the
> train stations.  The closest is Leysin-Feydey, though you may also go
> down in Versmont if you prefer less steep streets.  It's around 10-15
> minutes to walk.  There is also a free bus touring the village hourly.
>
> * if you were there in previous years: the Chalet to go to is the
> "bottom" one.  Go past the "top" one for 100m more, then back to the
> right 100m.
>
> * if you arrive Saturday before 5pm, meet me at L'Essentiel, a new
> restaurant nearby.  If you arrive afterwards, go to the Chalet
> directly.
>
> * L'Essentiel is in the same place as an old restaurant which I'll not
> name here: google maps is not up-to-date, so it has only the old
> restaurant --- but it is misplaced...
>
>
> A bient?t,
>
> Armin.
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev

From arigo at tunes.org  Tue Feb 16 10:53:44 2016
From: arigo at tunes.org (Armin Rigo)
Date: Tue, 16 Feb 2016 16:53:44 +0100
Subject: [pypy-dev] Leysin Sprint: instructions
In-Reply-To: <CAK5idxQJkiC9itLjf2J2Xb8VTgMMkCbzuRcgZtV8QMXuk2jtFw@mail.gmail.com>
References: <CAMSv6X3rbjEpU+-iwP=KB+QNuKWBRzaPGNi0cEvEapTPdwTD7w@mail.gmail.com>
 <CAK5idxQJkiC9itLjf2J2Xb8VTgMMkCbzuRcgZtV8QMXuk2jtFw@mail.gmail.com>
Message-ID: <CAMSv6X08bp7XpkCiK+D_jUPr=iD7XOUA02UVEgKcWwCorr-6+A@mail.gmail.com>

Hi,

On Tue, Feb 16, 2016 at 2:53 PM, Maciej Fijalkowski <fijall at gmail.com> wrote:
> Armin, is L'essentiel on open street map at the right spot?

Yes, I've put it there myself when the place opened :-)


Armin

From g3orge.app at gmail.com  Tue Feb 16 18:23:07 2016
From: g3orge.app at gmail.com (George Papanikolaou)
Date: Wed, 17 Feb 2016 01:23:07 +0200
Subject: [pypy-dev] Partial Escape Analysis and Scalar Replacement
Message-ID: <CAByyCQCH98v5PLuAZ3gSy0QLctyQZP4gKYRdueVP8RvV-PwDHA@mail.gmail.com>

Hey list,

I'd like to announce that I will attempt to implement an optimization technique
in PyPy as part of my thesis for my CS diplomma.

In addition to the local advisor from my uni, Carl Friedrich Bolz (@cfbolz)
accepted to "mentor" me for the attempt.

I'll be reporting the progress frequently here (so you will hear soon more
details) and of course I'll also be availabe on the IRC channel, which I'll
also use for the daily communication with Carl and for any other questions or
problems I may have with the codebase.

The optimization is based on the paper "Partial Escape Analysis and Scalar
Replacement on Java" by L. Stadler, T. W?rthinger and H. M?ssenb?ck.

Feel free to add any comments, remarks, ideas, etc. Have a good day.

Cheers,
George

--
George 'papanikge' Papanikolaou

From amauryfa at gmail.com  Wed Feb 17 04:45:43 2016
From: amauryfa at gmail.com (Amaury Forgeot d'Arc)
Date: Wed, 17 Feb 2016 10:45:43 +0100
Subject: [pypy-dev] Partial Escape Analysis and Scalar Replacement
In-Reply-To: <CAByyCQCH98v5PLuAZ3gSy0QLctyQZP4gKYRdueVP8RvV-PwDHA@mail.gmail.com>
References: <CAByyCQCH98v5PLuAZ3gSy0QLctyQZP4gKYRdueVP8RvV-PwDHA@mail.gmail.com>
Message-ID: <CAGmFidYZAQakv-ED_Um=Ae+1npLfNxV2Z8z+tZdSCaWZXOYSvg@mail.gmail.com>

Hi George,

2016-02-17 0:23 GMT+01:00 George Papanikolaou <g3orge.app at gmail.com>:

> Hey list,
>
> I'd like to announce that I will attempt to implement an optimization
> technique
> in PyPy as part of my thesis for my CS diplomma.


Welcome to PyPy development!
PyPy was designed upfront to experiment with new development techniques,
and we always need more speed :-)

I wish you good luck!


>

In addition to the local advisor from my uni, Carl Friedrich Bolz (@cfbolz)
> accepted to "mentor" me for the attempt.
>
> I'll be reporting the progress frequently here (so you will hear soon more
> details) and of course I'll also be availabe on the IRC channel, which I'll
> also use for the daily communication with Carl and for any other questions
> or
> problems I may have with the codebase.
>
> The optimization is based on the paper "Partial Escape Analysis and Scalar
> Replacement on Java" by L. Stadler, T. W?rthinger and H. M?ssenb?ck.
>
> Feel free to add any comments, remarks, ideas, etc. Have a good day.
>
> Cheers,
> George
>
> --
> George 'papanikge' Papanikolaou
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>



-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160217/d09b526e/attachment.html>

From arigo at tunes.org  Wed Feb 17 06:07:56 2016
From: arigo at tunes.org (Armin Rigo)
Date: Wed, 17 Feb 2016 12:07:56 +0100
Subject: [pypy-dev] Looking for clues to consistent Seg Fault in PyPy
 2.6.1
In-Reply-To: <CAMSv6X2rUK7_xPmQZpQwaARpmgjWjJkynx7MXietwCyDaPSNsg@mail.gmail.com>
References: <CAFsQrzAj0++9AuJ-2YMmMY_vMh1JHbGD5cD-t_bvm1X2O0KdDQ@mail.gmail.com>
 <CAMSv6X0RUmnpBm0bNNyExrFpbySz9Z-ZaSY3dDSJu1O-ai0yfQ@mail.gmail.com>
 <CAFsQrzARTEiHNDotbqRF_8-Wvy6JLM7o0eJGXgCVGuZCbVB=8w@mail.gmail.com>
 <CAMSv6X0Q_cNTruxH+Yd67Y4SRDAEG-ygc+d3feOVDDSUqOBzMg@mail.gmail.com>
 <CAGmFidYp_Pz37671OuMDpuhufYMXy6-k5H2Xvz49=WmovjyrxQ@mail.gmail.com>
 <CAMSv6X3LjwgFasc9G-C=uhcJQm6SAe9PsU8kS5NQ7QaNq29_Vw@mail.gmail.com>
 <CAFsQrzDEjN3Gs1apzC9g9vFfFpj0Ck_8f5Hx5Uak=dXQYE8Jkw@mail.gmail.com>
 <CAMSv6X0COcCpp_NT0B6g6UHnXwWDiyAenbxANA+PTbnwwX05wA@mail.gmail.com>
 <n1mkbr$jh2$1@ger.gmane.org>
 <CAMSv6X2rUK7_xPmQZpQwaARpmgjWjJkynx7MXietwCyDaPSNsg@mail.gmail.com>
Message-ID: <CAMSv6X1mUacRSuiGJZcR_=K75VYy3z+k4UVQt3_h7VM0HRa+iQ@mail.gmail.com>

Hi Stefan,

On 8 November 2015 at 09:40, Armin Rigo <arigo at tunes.org> wrote:
> On Sun, Nov 8, 2015 at 5:51 AM, Stefan Behnel <stefan_ml at behnel.de> wrote:
>> I tried to simply disable the special casing in proxy.pxi, but it only
>> leads to more crashes:
>
> Yes, it is expected.  The special-casing was introduced because PyPy
> doesn't guarantee the identity of "PyObject *" when you don't own a
> refcount.  It's what I'm trying to fix in the branch cpyext-gc-support
> but it's not done yet.  It's why I said I don't know how to tweak lxml
> to make it work on current versions of PyPy.

The PyPy branch "cpyext-gc-support-2" should work (it isn't much
tested so far).  We should try
to run https://github.com/lxml/lxml/tree/pypy4 in it.  I'm writing
this mail now because I'm hitting a chain of semi-related problems and
I need a break, but would welcome other people trying in my stead :-)


A bient?t,

Armin.

From me at manueljacob.de  Thu Feb 18 06:13:06 2016
From: me at manueljacob.de (Manuel Jacob)
Date: Thu, 18 Feb 2016 12:13:06 +0100
Subject: [pypy-dev] Partial Escape Analysis and Scalar Replacement
In-Reply-To: <CAByyCQCH98v5PLuAZ3gSy0QLctyQZP4gKYRdueVP8RvV-PwDHA@mail.gmail.com>
References: <CAByyCQCH98v5PLuAZ3gSy0QLctyQZP4gKYRdueVP8RvV-PwDHA@mail.gmail.com>
Message-ID: <964e5679b3a49a7f55ae6cddb8d8edb1@indus.uberspace.de>

Hi George,

Do you plan to implement the technique for the JIT or for the static 
compilation toolchain ("RPython translator")?

-Manuel

On 2016-02-17 00:23, George Papanikolaou wrote:
> Hey list,
> 
> I'd like to announce that I will attempt to implement an optimization 
> technique
> in PyPy as part of my thesis for my CS diplomma.
> 
> In addition to the local advisor from my uni, Carl Friedrich Bolz 
> (@cfbolz)
> accepted to "mentor" me for the attempt.
> 
> I'll be reporting the progress frequently here (so you will hear soon 
> more
> details) and of course I'll also be availabe on the IRC channel, which 
> I'll
> also use for the daily communication with Carl and for any other 
> questions or
> problems I may have with the codebase.
> 
> The optimization is based on the paper "Partial Escape Analysis and 
> Scalar
> Replacement on Java" by L. Stadler, T. W?rthinger and H. M?ssenb?ck.
> 
> Feel free to add any comments, remarks, ideas, etc. Have a good day.
> 
> Cheers,
> George
> 
> --
> George 'papanikge' Papanikolaou
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev

From kunalgrover05 at gmail.com  Thu Feb 18 17:28:26 2016
From: kunalgrover05 at gmail.com (Kunal Grover)
Date: Fri, 19 Feb 2016 03:58:26 +0530
Subject: [pypy-dev] Google Summer of Code ideas
Message-ID: <CAF39Kz_fHp+Dc+w6bmRjMhtrwDybP8XcAWKMk-Ss3HcqjGbqqg@mail.gmail.com>

Hi,

I am interested to work with PyPy on a GSoC project. PyPy is still not
present as a registered subproject on the Python page, so I wanted to ask
on the list if someone is willing to mentor me.
Are the tasks listed on the project ideas page up to date? What would be
some of the projects that would be very beneficial for PyPy?

Thank you.
Kunal Grover
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160219/df8da558/attachment.html>

From fijall at gmail.com  Fri Feb 19 02:55:27 2016
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Fri, 19 Feb 2016 08:55:27 +0100
Subject: [pypy-dev] Google Summer of Code ideas
In-Reply-To: <CAF39Kz_fHp+Dc+w6bmRjMhtrwDybP8XcAWKMk-Ss3HcqjGbqqg@mail.gmail.com>
References: <CAF39Kz_fHp+Dc+w6bmRjMhtrwDybP8XcAWKMk-Ss3HcqjGbqqg@mail.gmail.com>
Message-ID: <CAK5idxR7YqASVg6bvwuFuBNV2JX=oTnAJNZD2H1ki7bUiDt2OA@mail.gmail.com>

Hi Kunal

We'll only register PyPy after PSF is officially registered with
google (it'll only happen by the end of Feb)

Did you look at the project ideas on
http://doc.pypy.org/en/latest/project-ideas.html?

On Thu, Feb 18, 2016 at 11:28 PM, Kunal Grover <kunalgrover05 at gmail.com> wrote:
> Hi,
>
> I am interested to work with PyPy on a GSoC project. PyPy is still not
> present as a registered subproject on the Python page, so I wanted to ask on
> the list if someone is willing to mentor me.
> Are the tasks listed on the project ideas page up to date? What would be
> some of the projects that would be very beneficial for PyPy?
>
> Thank you.
> Kunal Grover
>
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>

From kunalgrover05 at gmail.com  Fri Feb 19 03:26:57 2016
From: kunalgrover05 at gmail.com (Kunal Grover)
Date: Fri, 19 Feb 2016 13:56:57 +0530
Subject: [pypy-dev] Google Summer of Code ideas
In-Reply-To: <CAK5idxR7YqASVg6bvwuFuBNV2JX=oTnAJNZD2H1ki7bUiDt2OA@mail.gmail.com>
References: <CAF39Kz_fHp+Dc+w6bmRjMhtrwDybP8XcAWKMk-Ss3HcqjGbqqg@mail.gmail.com>
 <CAK5idxR7YqASVg6bvwuFuBNV2JX=oTnAJNZD2H1ki7bUiDt2OA@mail.gmail.com>
Message-ID: <CAF39Kz-237jv0bNkEppVnFEStHtBNaq9TXAakDW1XV93R9BfXQ@mail.gmail.com>

Hi Maciej,

Thanks for your reply. I checked out the ideas on the page, my current
interests are in:
1- Improvements in Numpy and Matplotlib integration
2- Building a garbage collector

I am looking for something that helps add something really useful to PyPy.
What would be good resources for approaching these problems? Should the
focus be to look at some theoretical basis or some code implementations
which solve similar problems?

On Fri, Feb 19, 2016 at 1:25 PM, Maciej Fijalkowski <fijall at gmail.com>
wrote:

> Hi Kunal
>
> We'll only register PyPy after PSF is officially registered with
> google (it'll only happen by the end of Feb)
>
> Did you look at the project ideas on
> http://doc.pypy.org/en/latest/project-ideas.html?
>
> On Thu, Feb 18, 2016 at 11:28 PM, Kunal Grover <kunalgrover05 at gmail.com>
> wrote:
> > Hi,
> >
> > I am interested to work with PyPy on a GSoC project. PyPy is still not
> > present as a registered subproject on the Python page, so I wanted to
> ask on
> > the list if someone is willing to mentor me.
> > Are the tasks listed on the project ideas page up to date? What would be
> > some of the projects that would be very beneficial for PyPy?
> >
> > Thank you.
> > Kunal Grover
> >
> >
> > _______________________________________________
> > pypy-dev mailing list
> > pypy-dev at python.org
> > https://mail.python.org/mailman/listinfo/pypy-dev
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160219/c5c33962/attachment.html>

From cfbolz at gmx.de  Mon Feb 22 02:06:59 2016
From: cfbolz at gmx.de (Carl Friedrich Bolz)
Date: Mon, 22 Feb 2016 08:06:59 +0100
Subject: [pypy-dev] Partial Escape Analysis and Scalar Replacement
In-Reply-To: <964e5679b3a49a7f55ae6cddb8d8edb1@indus.uberspace.de>
References: <CAByyCQCH98v5PLuAZ3gSy0QLctyQZP4gKYRdueVP8RvV-PwDHA@mail.gmail.com>
 <964e5679b3a49a7f55ae6cddb8d8edb1@indus.uberspace.de>
Message-ID: <56CAB393.6090409@gmx.de>

Hi Manuel,

as the one who suggested the paper in the first place, the goal would be 
to add it to the RPython translator.

(it's not useful in the JIT, virtuals already provide partial escape 
analysis there).

Cheers,

Carl Friedrich

On 18/02/16 12:13, Manuel Jacob wrote:
> Hi George,
>
> Do you plan to implement the technique for the JIT or for the static
> compilation toolchain ("RPython translator")?
>
> -Manuel


From kunalgrover05 at gmail.com  Tue Feb 23 13:21:41 2016
From: kunalgrover05 at gmail.com (Kunal Grover)
Date: Tue, 23 Feb 2016 23:51:41 +0530
Subject: [pypy-dev] Google Summer of Code ideas
In-Reply-To: <CAF39Kz-237jv0bNkEppVnFEStHtBNaq9TXAakDW1XV93R9BfXQ@mail.gmail.com>
References: <CAF39Kz_fHp+Dc+w6bmRjMhtrwDybP8XcAWKMk-Ss3HcqjGbqqg@mail.gmail.com>
 <CAK5idxR7YqASVg6bvwuFuBNV2JX=oTnAJNZD2H1ki7bUiDt2OA@mail.gmail.com>
 <CAF39Kz-237jv0bNkEppVnFEStHtBNaq9TXAakDW1XV93R9BfXQ@mail.gmail.com>
Message-ID: <CAF39Kz-Wx0d4GpuLQgwez7ajvsY3xgXx+4duQOtaabLo1=SWLQ@mail.gmail.com>

I am currently looking at the Numpy project, and would like to work on
improvements on both the PyPy and PyPy3 versions. What could be some part
of the project I should be looking at initially? Should I try fixing Numpy
for PyPy3 or look at some issues?

<http://about.me/kunalgrover05>


*Kunal Grover*
about.me/kunalgrover05

<http://about.me/kunalgrover05> <http://about.me/kunalgrover05>
<http://about.me/kunalgrover05>


On Fri, Feb 19, 2016 at 1:56 PM, Kunal Grover <kunalgrover05 at gmail.com>
wrote:

> Hi Maciej,
>
> Thanks for your reply. I checked out the ideas on the page, my current
> interests are in:
> 1- Improvements in Numpy and Matplotlib integration
> 2- Building a garbage collector
>
> I am looking for something that helps add something really useful to PyPy.
> What would be good resources for approaching these problems? Should the
> focus be to look at some theoretical basis or some code implementations
> which solve similar problems?
>
> On Fri, Feb 19, 2016 at 1:25 PM, Maciej Fijalkowski <fijall at gmail.com>
> wrote:
>
>> Hi Kunal
>>
>> We'll only register PyPy after PSF is officially registered with
>> google (it'll only happen by the end of Feb)
>>
>> Did you look at the project ideas on
>> http://doc.pypy.org/en/latest/project-ideas.html?
>>
>> On Thu, Feb 18, 2016 at 11:28 PM, Kunal Grover <kunalgrover05 at gmail.com>
>> wrote:
>> > Hi,
>> >
>> > I am interested to work with PyPy on a GSoC project. PyPy is still not
>> > present as a registered subproject on the Python page, so I wanted to
>> ask on
>> > the list if someone is willing to mentor me.
>> > Are the tasks listed on the project ideas page up to date? What would be
>> > some of the projects that would be very beneficial for PyPy?
>> >
>> > Thank you.
>> > Kunal Grover
>> >
>> >
>> > _______________________________________________
>> > pypy-dev mailing list
>> > pypy-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pypy-dev
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160223/2b0616ae/attachment.html>

From techtonik at gmail.com  Wed Feb 24 05:05:35 2016
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 24 Feb 2016 13:05:35 +0300
Subject: [pypy-dev] mingwpy
Message-ID: <CAPkN8xLs08tQ+5+_wAKRPcCG1B9dcxFcux5zG3W5rNaK0=+T2A@mail.gmail.com>

I am not sure if CFFI list a better place to post about this one, but
it seems to me that you may be interested in the initiative to create
GCC that can link to MS VS runtimes.

Probably it can be used to cross-compile right stubs for
interoperability with C code on Windows platform.

https://mingwpy.github.io/
https://groups.google.com/forum/#!topic/mingwpy/z6TMklH56w8
-- 
anatoly t.