[pypy-dev] pypy-dev Digest, Vol 27, Issue 14

Kunal Puri kunal.r.puri at gmail.com
Sat Jul 20 18:20:03 CEST 2013 

Well i would love to meet you so do let me know. I came home this evening
amidst heavy rain and all. The weather here just seems to get worse each
year.  Was on my way back when i read the news.

Your provine or not. I think its terrible when circumstances push you to
such an extreme to do such a thing.

105  days! Wow. Thats a long time. I hope it isnt much longer now. Love you
babe..and ill speak to you on mon...
On Jul 20, 2013 3:32 PM, <pypy-dev-request at python.org> wrote:

> Send pypy-dev mailing list submissions to
>         pypy-dev at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mail.python.org/mailman/listinfo/pypy-dev
> or, via email, send a message with subject or body 'help' to
>         pypy-dev-request at python.org
>
> You can reach the person managing the list at
>         pypy-dev-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pypy-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: asmgcc assertion error in lang-smalltalk (Lars Wassermann)
>    2. Re: asmgcc assertion error in lang-smalltalk (Carl Friedrich Bolz)
>    3. Announcement: PyPy London Sprint (August 26 - September   1
>       2013) (Carl Friedrich Bolz)
>    4. Re: asmgcc assertion error in lang-smalltalk (Armin Rigo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 19 Jul 2013 12:28:40 +0200
> From: Lars Wassermann <lars.wassermann at student.hpi.uni-potsdam.de>
> To: <pypy-dev at python.org>
> Subject: Re: [pypy-dev] asmgcc assertion error in lang-smalltalk
> Message-ID: <51E914D8.8050205 at student.hpi.uni-potsdam.de>
> Content-Type: text/plain; charset="ISO-8859-1"
>
> On 07/19/2013 11:51 AM, Carl Friedrich Bolz wrote:
> > On 19/07/13 11:36, Lars Wassermann wrote:
> >> Hello,
> >> in the project lang-smalltalk, we have a problem we don't know where
> >> exactly the source may be.
> >> When running the VM with jit, we get:
> >>
> >> PyPy assertion failed at rpython_memory_gctransform_asmgcroot.c:583:
> >> in pypy_g_locate_caller_based_on_retaddr: found a stack frame that does
> >> not belong anywhere I know, bug in asmgcc
> >> Aborted (core dumped)
> >>
> >> When running without jit, everything works fine.
> >>
> >> Is the fact that the error only occurs when using the JIT a hint that
> >> the bug may not be in asmgcc?
> >
> > You can try to see whether it goes away when not using asmgcc, by
> > translating with:
> >
> > rpython --gcrootfinder=shadowstack -Ojit ...target...
> >
> > Cheers,
> >
> > Carl Friedrich
> > _______________________________________________
> > pypy-dev mailing list
> > pypy-dev at python.org
> > http://mail.python.org/mailman/listinfo/pypy-dev
> >
> That fixed the problem. Is there a way to generate a bug report for
> asmgcc, or would that be too complicated?
>
> Thank you,
> Lars
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 19 Jul 2013 12:44:39 +0200
> From: Carl Friedrich Bolz <cfbolz at gmx.de>
> To: pypy-dev at python.org
> Subject: Re: [pypy-dev] asmgcc assertion error in lang-smalltalk
> Message-ID: <51E91897.3080402 at gmx.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 19/07/13 12:28, Lars Wassermann wrote:
> > On 07/19/2013 11:51 AM, Carl Friedrich Bolz wrote:
> >> You can try to see whether it goes away when not using asmgcc, by
> >> translating with:
> >>
> >> rpython --gcrootfinder=shadowstack -Ojit ...target...
> >
> > That fixed the problem. Is there a way to generate a bug report for
> > asmgcc, or would that be too complicated?
>
> What do you mean? You can add one to bugs.pypy.org (asmgcc is part of
> PyPy).
>
> Cheers,
>
> Carl Friedrich
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 19 Jul 2013 15:47:35 +0200
> From: Carl Friedrich Bolz <cfbolz at gmx.de>
> To: pypy-dev at python.org
> Subject: [pypy-dev] Announcement: PyPy London Sprint (August 26 -
>         September       1 2013)
> Message-ID: <51E94377.2060006 at gmx.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> =====================================================================
>          PyPy London Sprint (August 26 - September 1 2013)
> =====================================================================
>
> The next PyPy sprint will be in London, United Kingdom for the first
> time. This is a fully public sprint. PyPy sprints are a very good way
> to get into PyPy development and no prior PyPy knowledge is necessary.
>
>
> ------------------------------
> Goals and topics of the sprint
> ------------------------------
>
> For newcomers:
>
> * bring your application/library and we'll help you port it to PyPy,
>   benchmark and profile
>
> * come and write your favorite missing numpy function
>
> * help us work on developer tools like jitviewer
>
> We'll also work on:
>
> * refactoring the JIT optimizations
>
> * STM and STM-related topics
>
> * anything else attendees are interested in
>
> -----------
> Exact times
> -----------
>
> The work days should be August 26 - September 1 2013 (Monday-Sunday).
> The official plans are for people to arrive on the 26th, and
> to leave on the 2nd. There will be a break day in the middle.
> We'll typically start at 10:00 in the morning.
>
>
> ------------
> Location
> ------------
>
> The sprint will happen within a room of `King's College's`_ `Strand
> Campus`_ in `Central London, UK`_. There are some travel instructions
> `how to
> get there`_. We are being hosted by `Laurence Tratt`_ and the `Software
> Development Team`_.
>
> .. _`King's College's`: http://www.kcl.ac.uk/
> .. _`Central London, UK`: http://goo.gl/maps/Qz0zz
> .. _`Strand Campus`:
> http://www.kcl.ac.uk/campuslife/campuses/strand/StrandCampusLocation.aspx
> .. _`how to get there`:
> http://www.kcl.ac.uk/campuslife/campuses/directions/strand.aspx
> .. _`Laurence Tratt`: http://tratt.net/laurie
> .. _`Software Development Team`: http://soft-dev.org
>
> ------------
> Demo Session
> ------------
>
> If you don't want to come to the full sprint, but still want to chat a
> bit, we are planning to have a demo session on Tuesday August 27. We
> will announce this separately on the blog. If you are interested, please
> leave a comment.
>
> --------------
> Registration
> --------------
>
> If you want to attend, please register by adding yourself to the
> "people.txt" file in Mercurial::
>
>   https://bitbucket.org/pypy/extradoc/
>   https://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/london-2013
>
> or on the pypy-dev mailing list if you do not yet have check-in rights::
>
>   http://mail.python.org/mailman/listinfo/pypy-dev
>
> Remember that you may need a (insert country here)-to-UK power adapter.
> Please note that UK is not within the Schengen zone, so non-EU and
> non-Switzerland citizens may require specific visa. Please check `travel
> regulations`_. Also, the UK uses pound sterling (GBP).
>
> .. _`travel regulations`:
> http://www.ukba.homeoffice.gov.uk/visas-immigration/do-you-need-a-visa/
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 20 Jul 2013 09:32:31 +0200
> From: Armin Rigo <arigo at tunes.org>
> To: Lars Wassermann <lars.wassermann at student.hpi.uni-potsdam.de>
> Cc: PyPy Developer Mailing List <pypy-dev at python.org>
> Subject: Re: [pypy-dev] asmgcc assertion error in lang-smalltalk
> Message-ID:
>         <CAMSv6X1j8xomZjLLE9JZKT+9h65hrCH=
> xwvU+KStJOxL88ja3Q at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Lars,
>
> On Fri, Jul 19, 2013 at 11:36 AM, Lars Wassermann
> <lars.wassermann at student.hpi.uni-potsdam.de> > PyPy assertion failed
> at rpython_memory_gctransform_asmgcroot.c:583:
> > in pypy_g_locate_caller_based_on_retaddr: found a stack frame that does
> > not belong anywhere I know, bug in asmgcc
>
> The best report for us would be to include exactly on which precise OS
> this occurs, with which exact version of GCC, and the exact source
> code (url and revision number); and the example that crashes.  Then we
> hope that the bug is really reproducible, which might not be the case.
>
> You can also try to give us the binary, and we attempt to run it.
>
> Failing that, you need to debug yourself the crash, which I can
> explain how to do (but is not trivial).
>
>
> A bient?t,
>
> Armin.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> http://mail.python.org/mailman/listinfo/pypy-dev
>
>
> ------------------------------
>
> End of pypy-dev Digest, Vol 27, Issue 14
> ****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20130720/c86762ed/attachment.html>

More information about the pypy-dev mailing list