My results differ. If you want more systematic approach for QA and security (the recent paranoia induced by the xz backdoor) you will need moderate budget possibly with zero trust to me.
Have a nice weekend. On Fri, Apr 12, 2024 at 3:52 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > > > On 12 April 2024 12:42:39 CEST, Georgi Guninski <ggunin...@gmail.com> wrote: > >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. > > Well, in all my tries the crash happened in the same place, the place that > now is no longer reachable. > > And the reason for the crash was, AFAIU, due to calling a plain Python code > (where Ctrl-C was caught) from a "noexcept" Cython code. That is, it's a > crash due to inability to properly process Ctrl-C. > > How many more similar places are left there in Cython code in Sage, I don't > know. > > Dima > > > >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/C701D76E-A116-4D83-B427-24C305F51201%40gmail.com. -- 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_ObgEtxC3Ok7%2BtHE174HS8kiUzbTC0y8%3D5Wdp%2B1QjNQw%40mail.gmail.com.
