Processed: Re: Bug#863919: Acknowledgement (sympow segfaults with basic input)
Processing control commands: > severity -1 minor Bug #863919 [sympow] sympow segfaults with basic input Severity set to 'minor' from 'important' > retitle -1 segfaults when MALLOC_PERTURB_ is set Bug #863919 [sympow] sympow segfaults with basic input Changed Bug title to 'segfaults when MALLOC_PERTURB_ is set' from 'sympow segfaults with basic input'. -- 863919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#863919: Acknowledgement (sympow segfaults with basic input)
Control: severity -1 minor Control: retitle -1 segfaults when MALLOC_PERTURB_ is set Hi Jerome, it happens on stretch/sid. This is what I have installed: Versions of packages sympow depends on: ii dpkg 1.18.24 ii libc62.24-10 ii pari-gp 2.9.1-1 ii sympow-data 1.023-8 However, I just did some more tests and have tracked this down to me setting MALLOC_PERTURB_ in my .xsession. The error goes away if I unset it: $ env -u MALLOC_PERTURB_ sympow -curve "[0,-1,1,-10,-20]" -analrank [..] Done with small primes 1049 Analytic Rank is 0 : L-value 2.53842e-01 $ sympow -curve "[0,-1,1,-10,-20]" -analrank [..] Done with small primes 1049 Segmentation fault 139 MALLOC_PERTURB_ is a glibc envvar that causes malloc() and free() to set memory - see "man mallopt" - which I was testing locally to see if it might be a good security defense against attacks like HeartBleed and Cloudbleed. Since it's not a default envvar that most users would set, I'll downgrade the severity of this bug. However I haven't experienced any problems with other programs, so I would guess that sympow is using malloc/free in a weird way, which may be worth revisiting if you have time. X Jerome BENOIT: > Hello Ximin, thanks for your report. > > Do you meant that the issue happens on Stretch ? > I ask because I thought it happens on experimental and because the CI test > does not currently fail. > > Thanks, > Jerome > > On 02/06/17 14:34, Ximin Luo wrote: >> BTW the stretch release date is soon: > >> https://lists.debian.org/debian-devel-announce/2017/05/msg2.html > >> The deadline for fixing this is June 9th and you'll need to file an unblock >> request, asking them to reduce the default migration time of 10 days. > >> I'm not sure if this bug warrants raising the severity to grave, but please >> do that if appropriate. > >> X > > > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#863919: Acknowledgement (sympow segfaults with basic input)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Ximin, thanks for your report. Do you meant that the issue happens on Stretch ? I ask because I thought it happens on experimental and because the CI test does not currently fail. Thanks, Jerome On 02/06/17 14:34, Ximin Luo wrote: > BTW the stretch release date is soon: > > https://lists.debian.org/debian-devel-announce/2017/05/msg2.html > > The deadline for fixing this is June 9th and you'll need to file an unblock > request, asking them to reduce the default migration time of 10 days. > > I'm not sure if this bug warrants raising the severity to grave, but please > do that if appropriate. > > X > - -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B -BEGIN PGP SIGNATURE- iQQcBAEBCgAGBQJZMWLvAAoJED+SGaZ/NsaLzKcgAIbaY2alYqcF06036CrluaRU rl4cMLa+9vPXwetoiZzeU8Abhl17zZohJOro48a7SsmfrXRU3G5sARoXww9NTCbm 5cPH2oyijZxrLIe3lgp92fL+dDgDCbMOBgkDIAQa2H9hvFa1YhNhyQqOIfpW2/1i ubZJiRRb9N1fJ5+CZQD//3FFDIX64gC/kt7Tah1E1Yq5e7pHnEWeLTB+TSJrGJEs T0WCQ+8kVMvIfjWiyOhsmdRyryqSbXnrK93rmb2nvXqUcaTF+zWT9NoP+jRgfs4e jNTggACPPGd04wccT/0PHELH9qQ1lNM0x4yFYumwPcrf51TD3jT/XeuDawABYuR7 Q7reWy89Ab0gkMXki0epKDwkSe2NgTQPSoKv0m3Rud7Cd2M+hnuIyl/91VeHQeXy o5kDLxsvE4eMdfpZGhiKZ2jp1J7KFhx0hQxVxQYgCXl7BWCUDbZ9XAREKvKx9Zpn acO1Fz9Sg210xHyet0HyjnpqF3We9wWIdMgWm0D4r/1Uxp5fGWyG58O39QSaZwKe NfIeMCn0rOr4OP/bkkPS4Skl40RYxdvOyOxrUZ/m0oJfi79hC5ffCJVnWFIZKpeb kLi0OIJUuF8qrvNAila8AdlpG4q/GYdpJimXiOr6RZav4QACIfh/gdea+vXc3JD9 ghq6F5R/kGBbWsqEuSfi+hUxPm5P41lWAhcDLXXR6JNDVLFmUUXqx6BM+wcs6rrJ kiUSmthzXO4ysrq19DlJd5iUPSHYmI0Nzr5vhG/Nm55dveOcWs2q8EbHPo1rFDvA yUQxb0Z9JHfTX4Qd8YOCg+WHl7cEK4bP7nA2/s3LK9vmC/Qy8bFkgOcXAoNrosGb JkrNXywZn9vP8/RdtV8PGVQKOwhmWJcMmvkqffWJckmJWj6AfGoqepDWxJMKSwBM Z3PWlaW/lPLqt1l5csw0jue2rfrX4fNJKVBRfm28zFRBHdSzV8FtEgFS5nPcVs0e 6wtqWNcbnlXLePuaQbBSd+xtgqDG2+mtbWwR/9FSU7zcc72PVFt3BSz5F9A+dIJl uyDgkb06laSkfAfzGlbC5G/J8fMK0nyMOfla2NOa224o7nB8/mQXZlWzaBTbdwdF QoDVMnc1sys4nayKETTD6kyhrDnPxoFjUF0zkERjncmjs2Bqf2HdgLqN32DDXvVW jdICM7iuQOeG1Xrj4x7gWtkDufLhCH1NuPcbypojV8Etur6j5ESf2ZTaRF6NowxR 1j6f6YaaocAGwwmWW88NJ2qCDgf1ber72VeL7q2babwzc4LgDCsbXnYSMYUNs9Q7 kbu2DbI5yT6EYJNkRwB0mDjnF0MA8YshmPtsijYvquOAY7aItoGv2gRaiBQ9XwU= =0Msq -END PGP SIGNATURE- -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#863919: Acknowledgement (sympow segfaults with basic input)
BTW the stretch release date is soon: https://lists.debian.org/debian-devel-announce/2017/05/msg2.html The deadline for fixing this is June 9th and you'll need to file an unblock request, asking them to reduce the default migration time of 10 days. I'm not sure if this bug warrants raising the severity to grave, but please do that if appropriate. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
