THanks for looking into this Jeroen (I hoped you would).  The file bug.gp
you attached causes an error in the latest gp (version 2.10.0), after
increasing parisizemax I get the same error message.  But I compiled that
more than a week ago so probably before we send a bug report upstream we
should test it on the latest pari git commit.

John

On 12 June 2018 at 22:08, Jeroen Demeyer <[email protected]> wrote:

> I haven't managed to reproduce it in GP, I have no idea why. Typically,
> it's not so hard to translate a Sage bug like this to a PARI/GP bug. It
> must be something rather subtle. I'll try again tomorrow.
>
> I did manage to reproduce it with the PARI-in-Sage by running the attached
> GP script in Sage:
>
> sage: pari('read("/tmp/bug.gp")')
> ------------------------------------------------------------
> ---------------
> PariError                                 Traceback (most recent call last)
> <ipython-input-1-d8453d83569e> in <module>()
> ----> 1 pari('read("/tmp/bug.gp")')
>
> cypari2/pari_instance.pyx in cypari2.pari_instance.Pari.__call__()
>
> cypari2/gen.pyx in cypari2.gen.objtogen()
>
> cypari2/handle_error.pyx in cypari2.handle_error._pari_err_handle()
>
> PariError: nffactor: bug in LLL_cmbf [no factor], please report
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to