[pypy-dev] unable to translate with current head of default

[Alex Gaynor]

On Tue, May 24, 2011 at 3:46 PM, <wlavrijsen at lbl.gov> wrote:

> Hi Maciej,
>
>  On Tue, May 24, 2011 at 7:09 AM,  <wlavrijsen at lbl.gov> wrote:
>>
>>> running into the following traceback when translating. Any ideas? My
>>> machine
>>> too old to have certain features? Thanks!
>>>
>> Should be fixed now, sorry
>>
>
> cool, now it translates again!
>
> Btw., the reason to move to head of default was b/c my translated pypy-c
> was
> crashing on the spot. The binary download of 1.5 and older locally
> translated
> pypy's didn't do that.
>
> Turns out there is something with my history file: the crash happens when
> it's
> being loaded by readline:
>
> Python 2.7.1 (9113640a83ac+8d950d4e5c98+, May 24 2011, 20:01:17)
> [PyPy 1.5.0-alpha0 with GCC 4.4.1] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> using my private settings ...
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x08aae11c in pypy_g_OptHeap_emitting_operation ()
>
> By playing a little, I find that the history file is problematic if it
> contains
> 1000 lines or more. Having 999 lines or less is fine either way.
>
> Doesn't matter for me now that I know, but it's rather odd.
>
> Best regards,
>           Wim
>
> --
> WLavrijsen at lbl.gov    --    +1 (510) 486 6411    --    www.lavrijsen.net
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> http://mail.python.org/mailman/listinfo/pypy-dev
>

Given that 1000 is the default cutoff for the JIT, and the gdb backtrace you
have, it's pretty clear that there's a crash during compilation, and that
readline loops over the lines in the history file, and hitting that 1000th
line triggers the compilation.

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20110524/002b2c3f/attachment.html>