Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-28 Thread Victor Stinner
Le jeudi 28 janvier 2010 08:31:50, Neal Norwitz a écrit : > Ben, thanks. Your comment gave me a great laugh and I really > appreciated it. :-) > > The chapter is about the general Python development process, including > testing, static analysis, dynamic analysis, including Fusil among > other thi

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-28 Thread Stefan Behnel
Neal Norwitz, 28.01.2010 08:31: > One of my points to Victor and everyone else like him is that even > though it may seem no one is listening to you or cares, you might be > surprised to find out how many people really are paying attention and > do care. If you have something you want to do, make

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-27 Thread Neal Norwitz
On Wed, Jan 27, 2010 at 11:58 AM, Ben Finney wrote: > Chris Bergstresser writes: > >> On Wed, Jan 27, 2010 at 2:54 AM, Ben Finney >> wrote: >> > Neal Norwitz writes: >> >> Who knows, someone might even write a book about Fusil someday >> >> about a topic as obscure as Beautiful Testing. :-) >>

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-27 Thread Ben Finney
Chris Bergstresser writes: > On Wed, Jan 27, 2010 at 2:54 AM, Ben Finney > wrote: > > Neal Norwitz writes: > >> Who knows, someone might even write a book about Fusil someday > >> about a topic as obscure as Beautiful Testing. :-) > > > > Your suggested title is already taken, though, for exac

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-27 Thread Chris Bergstresser
On Wed, Jan 27, 2010 at 2:54 AM, Ben Finney wrote: > Neal Norwitz writes: >> I definitely hope you continue to find and fix problems in Python. It >> helps everyone who uses Python even those who will never know to thank >> you. Who knows, someone might even write a book about Fusil someday >> ab

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-27 Thread Ben Finney
Neal Norwitz writes: > On Mon, Jan 25, 2010 at 2:34 PM, Victor Stinner > wrote: Along with others expressed here, you have my warm thanks, Victor, for your continuing efforts at fuzz testing Python and especially for careful reporting of the discovered bugs. > I definitely hope you continue to

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-27 Thread Neal Norwitz
On Mon, Jan 25, 2010 at 2:34 PM, Victor Stinner wrote: > > Interaction with the Python developers > == > > I open an issue for each bug found in CPython. I describe how to reproduce it > and try to write a patch. I have learn to always write an unit test, useful

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Terry Reedy
On 1/26/2010 2:27 AM, Terry Reedy wrote: On 1/25/2010 5:34 PM, Victor Stinner wrote: It looks like fuzzing bugs are not always appreciated by developers, maybe because they are always "borderline" cases (not "realist"). People grumble, sometimes, even when quietly appreciative. Sometimes, e

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Terry Reedy
On 1/25/2010 5:34 PM, Victor Stinner wrote: It looks like fuzzing bugs are not always appreciated by developers, maybe because they are always "borderline" cases (not "realist"). People grumble, sometimes, even when quietly appreciative. Sometimes, even if I write a patch, an unit test, expl

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread skip
Victor> Fuzzing is just one tool helping to improve the global security. Victor, Thank you, thank you, thank you. At my day job I work on automated trading systems. One key component of such tools is the safeguard subsystem which places limits on various parts of the system, the rates at w

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Victor Stinner
Hi, Le mardi 26 janvier 2010 00:40:47, Christian Heimes a écrit : > Victor Stinner wrote: > > I'm running regulary my fuzzer (Fusil) on CPython since summer 2008: I > > tested Python 2.5, 2.6, 2.7, 3.0, 3.1 and 3.2. I'm only looking for > > "fatal errors": Python process killed by a signal, or som

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Christian Heimes
Victor Stinner wrote: > I'm running regulary my fuzzer (Fusil) on CPython since summer 2008: I tested > Python 2.5, 2.6, 2.7, 3.0, 3.1 and 3.2. I'm only looking for "fatal errors": > Python process killed by a signal, or sometimes fuzzer timeouts. I ignore > most > timeout results because most

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Jesse Noller
On Mon, Jan 25, 2010 at 5:34 PM, Victor Stinner wrote: > Hi, > > I'm running regulary my fuzzer (Fusil) on CPython since summer 2008: I tested > Python 2.5, 2.6, 2.7, 3.0, 3.1 and 3.2. I'm only looking for "fatal errors": > Python process killed by a signal, or sometimes fuzzer timeouts. I ignore

Re: [Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor Stinner wrote: > Hi, > > I'm running regulary my fuzzer (Fusil) on CPython since summer 2008: I tested > Python 2.5, 2.6, 2.7, 3.0, 3.1 and 3.2. I'm only looking for "fatal errors": > Python process killed by a signal, or sometimes fuzzer tim

[Python-Dev] Summary of 2 years of Python fuzzing

2010-01-25 Thread Victor Stinner
Hi, I'm running regulary my fuzzer (Fusil) on CPython since summer 2008: I tested Python 2.5, 2.6, 2.7, 3.0, 3.1 and 3.2. I'm only looking for "fatal errors": Python process killed by a signal, or sometimes fuzzer timeouts. I ignore most timeout results because most of them are valid function c