Re: bugs about crashed with exit code 139
On 06/27/2013 03:58 PM, Andreas Tille wrote: Hi, On Thu, Jun 27, 2013 at 03:17:10PM +0200, olivier.sal...@codeless.fr wrote: Hi, you all have seen many many bugs from forallsecure, getting all the same crash exit code. Does anymore has a hint on the root cause of this? I can't imagine this does not come from the same root cause considering the numerous bugs found. here you can find some explanation: https://lists.debian.org/debian-devel/2013/06/msg00720.html and this is what I would regard as a reasonable action: https://lists.debian.org/debian-devel/2013/06/msg00796.html I forewarded some of the mails to three upstreams and will continue step by step. I personally did not even dived into the code to find some solution for a single bug and I hope we will be able to cooperate with upstream on this. I started to do the same on mobyle package, I will have a look at others this week-end. Kind regards Andreas. -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51cd5306.1060...@irisa.fr
bugs about crashed with exit code 139
Hi, you all have seen many many bugs from forallsecure, getting all the same crash exit code. Does anymore has a hint on the root cause of this? I can't imagine this does not come from the same root cause considering the numerous bugs found. Olivier -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51cc3b56.6030...@codeless.fr
Re: bugs about crashed with exit code 139
Hi, On Thu, Jun 27, 2013 at 03:17:10PM +0200, olivier.sal...@codeless.fr wrote: Hi, you all have seen many many bugs from forallsecure, getting all the same crash exit code. Does anymore has a hint on the root cause of this? I can't imagine this does not come from the same root cause considering the numerous bugs found. here you can find some explanation: https://lists.debian.org/debian-devel/2013/06/msg00720.html and this is what I would regard as a reasonable action: https://lists.debian.org/debian-devel/2013/06/msg00796.html I forewarded some of the mails to three upstreams and will continue step by step. I personally did not even dived into the code to find some solution for a single bug and I hope we will be able to cooperate with upstream on this. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130627135800.gb21...@an3as.eu
Re: bugs about crashed with exit code 139
On Thu, Jun 27, 2013 at 03:17:10PM +0200, olivier.sal...@codeless.fr wrote: you all have seen many many bugs from forallsecure, getting all the same crash exit code. Does anymore has a hint on the root cause of this? I can't imagine this does not come from the same root cause considering the numerous bugs found. See the thread Reporting 1.2K crashes on debian-devel. I did not look closely on any of the reports yet (and only reports in your own packages are available to you for now), but unless they are all crashing a common library, they are probably destinct. They are using a new automatic bug finding system, likely involving some fuzzing. Michael -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130627135959.gd27...@nighthawk.chemicalconnection.dyndns.org
