Re: SIGSEGV on isprime

Bill Allombert on Wed, 11 Jul 2018 17:25:51 +0200

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

Re: SIGSEGV on isprime

To: pari-users@pari.math.u-bordeaux.fr
Subject: Re: SIGSEGV on isprime
From: Bill Allombert <Bill.Allombert@math.u-bordeaux.fr>
Date: Wed, 11 Jul 2018 17:25:49 +0200
Delivery-date: Wed, 11 Jul 2018 17:25:51 +0200
In-reply-to: <9d5eadbe-7cdc-264b-e578-608e89d6781b@neuromancer.sk>
Mail-followup-to: pari-users@pari.math.u-bordeaux.fr
References: <372a72a9-4486-760d-02e4-e31d5e91bfd5@neuromancer.sk> <20180710215942.GE4112@yellowpig> <b1355d2d-7cba-af33-b2e6-75d7e4492ce4@neuromancer.sk> <5fb19e95-ee16-da8e-31c5-3f5a633b2762@neuromancer.sk> <9d5eadbe-7cdc-264b-e578-608e89d6781b@neuromancer.sk>
User-agent: Mutt/1.5.23 (2014-03-12)

On Wed, Jul 11, 2018 at 04:48:24PM +0200, Ján Jančár wrote:
> >> I have now tested:
> >>
> >> --enable-tls --kernel=none      --> works
> >> --enable-tls --kernel=none-gmp  --> SEGVs!
> >> --enalbe-tls --kernel=auto-none --> works

My guess is that there is a buffer overflow in the function
red_montgomery in the file src/kernel/gmp/mp.c which only
cause a SEGV when the stack ends on a page boundary.

At least I can reproduce this bug with valgrind now!

Thanks!
Bill.

Follow-Ups:
- Re: SIGSEGV on isprime
  - From: Karim Belabas <Karim.Belabas@math.u-bordeaux.fr>

References:
- SIGSEGV on isprime
  - From: Ján Jančár <johny@neuromancer.sk>
- Re: SIGSEGV on isprime
  - From: Bill Allombert <Bill.Allombert@math.u-bordeaux.fr>
- SIGSEGV on isprime
  - From: Ján Jančár <johny@neuromancer.sk>
- Re: SIGSEGV on isprime
  - From: Ján Jančár <johny@neuromancer.sk>
- Re: SIGSEGV on isprime
  - From: Ján Jančár <johny@neuromancer.sk>

Prev by Date: Re: SIGSEGV on isprime
Next by Date: Read/Write file on Android request.
Previous by thread: Re: SIGSEGV on isprime
Next by thread: Re: SIGSEGV on isprime
Index(es):
- Date
- Thread