On Fri, Apr 12, 2024 at 11:35 AM Dima Pasechnik <dimp...@gmail.com> wrote:
>
> This should be fixed by https://github.com/sagemath/sage/pull/37792
> please review
>
I suspect reproducing is hard, since it depends on the time of pressing CTL-C.
Also, lack a crash may be silent memory corruption.
It is weird that the crash is not always.
Do you fix the attached new testcase (no interaction required, may
need changing some constants)?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAGUWgD_5i%2BebLNsdJ4ZbaCuh_qcdMXtN2tkAaiByztA1oSOqTA%40mail.gmail.com.
"""
sage SEGV in solve_mod() + alarm() possibly related to signal
Author: Georgi Guninski
Fri Apr 12 09:49:15 AM UTC 2024
"""
def modcrash1(lim=100,seed=0):
#Author: Georgi Guninski
if seed != 0: set_random_seed(seed)
U=2000
L=U//2
x,y=var('x,y')
n=10**6
for i in range(lim):
S=randint(L,U)
print(i,S)
alarm(1.0*S/U)
try:
while True:
so=solve_mod(x*y-1,n)
cancel_alarm()
break
except: pass
cancel_alarm()
modcrash1()
