Re: bugs about "crashed with exit code 139"

2013-06-28 Thread Olivier Sallou
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

Re: bugs about "crashed with exit code 139"

2013-06-27 Thread Michael Banck
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

Re: bugs about "crashed with exit code 139"

2013-06-27 Thread Andreas Tille
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

bugs about "crashed with exit code 139"

2013-06-27 Thread olivier.sal...@codeless.fr
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.debia