Re: fflog seg fault

Bill Allombert on Fri, 01 Oct 2010 20:26:30 +0200

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: fflog seg fault

To: pari-users@list.cr.yp.to
Subject: Re: fflog seg fault
From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
Date: Fri, 1 Oct 2010 20:19:23 +0200
Delivery-date: Fri, 01 Oct 2010 20:26:30 +0200
In-reply-to: <AANLkTi=+nbpcsM3+UhhNBnW0kFgzxFxv94Rh91rsDkrZ@mail.gmail.com>
Mail-followup-to: pari-users@list.cr.yp.to
Mailing-list: contact pari-users-help@list.cr.yp.to; run by ezmlm
References: <AANLkTikTO7DyCX74mnjLzv2qUNueOrTXMnqv18utraJM@mail.gmail.com> <20101001103742.GA17575@yellowpig> <AANLkTim6jmD2nx3YKWpNFU3f_m-N7uR0H0XC3Co_=uhf@mail.gmail.com> <20101001140823.GC17575@yellowpig> <AANLkTi=+nbpcsM3+UhhNBnW0kFgzxFxv94Rh91rsDkrZ@mail.gmail.com>
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Oct 01, 2010 at 10:58:21AM -0400, Dan Bailey wrote:
> Thanks very much for clarifying usage of fflog!
> 
> Unfortunately, none of these suggestions (use a primitive root,
> provide the order, use the daily Windows snapshot binary with and
> without GMP) work on my platform.  They all produce the seg fault.

Ah yes, I can reproduce the bug under wine. It should be fixed in revision 12612.
Thanks for your bug report and your test.

Cheers,
Bill.

References:
- Re: fflog seg fault
  - From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
- Re: fflog seg fault
  - From: Dan Bailey <pets0undz@gmail.com>
- Re: fflog seg fault
  - From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
- Re: fflog seg fault
  - From: Dan Bailey <pets0undz@gmail.com>

Prev by Date: Re: fflog seg fault
Next by Date: Re: Integration
Previous by thread: Re: fflog seg fault
Next by thread: Problem with colors in .gprc
Index(es):
- Date
- Thread