|
From: Nicholas N. <nj...@cs...> - 2005-11-20 20:11:12
|
Hi, I've finally finished analysing the surveys. I attach two documents: 1. A high-level summary 2. A detailed report I plan to put these up on the site and email the user list about it, but I thought I'd run it past a few eyeballs before doing so. Let me know if you see any mistakes or things that should be changed. Thanks. Nick |
|
From: Julian S. <js...@ac...> - 2005-11-20 22:45:07
|
Wow. Excellent stuff. Thanks for doing all this. I now have total information overload :-) ---- summary: would benefit from a 1-sentence context setter of the form The survey, based at www.valgrind.org, ran from ... until ... NNN responses were received. ---- summary, Q9: I wasn't clear what "existing" platform category means. ---- report: typo, frong -> front ---- report: 9 (Valgrind on Other Platforms) [...] For this reason I think our main target platform of PPC32/MacOS X is still a good one; I think that will expose Valgrind to a large group of new users. In contrast, I think the overlap between Linux and BSD developers would be much higher, and so the underwhelming responses for BSD show that a BSD port would not achieve very much. An insightful piece of analysis. ---- report: Line 1800: incomplete sentence "There's" J |
|
From: Nicholas N. <nj...@cs...> - 2005-11-20 23:20:26
|
On Sun, 20 Nov 2005, Julian Seward wrote: > Wow. Excellent stuff. Thanks for doing all this. I now have total > information overload :-) So do I. Given the amount of effort involved (next time I'm going to make things a lot more automated!) I feel we didn't learn all that much. At least, there weren't any great surprises. But I guess that's a good sign, and it was still worth doing. Nick |
|
From: Josef W. <Jos...@gm...> - 2005-11-20 22:56:13
|
Hi Nick, truly excellent analysis. Thanks a lot, Josef On Sunday 20 November 2005 21:11, Nicholas Nethercote wrote: > Hi, > > I've finally finished analysing the surveys. I attach two documents: > > 1. A high-level summary > 2. A detailed report > > I plan to put these up on the site and email the user list about it, but I > thought I'd run it past a few eyeballs before doing so. Let me know if > you see any mistakes or things that should be changed. Thanks. > > Nick |
|
From: Tom H. <to...@co...> - 2005-11-21 09:51:58
|
In message <Pin...@ch...>
Nicholas Nethercote <nj...@cs...> wrote:
> I've finally finished analysing the surveys. I attach two documents:
>
> 1. A high-level summary
> 2. A detailed report
>
> I plan to put these up on the site and email the user list about it,
> but I thought I'd run it past a few eyeballs before doing so. Let me
> know if you see any mistakes or things that should be changed. Thanks.
All looks pretty good to me.
> - loading of debugging symbols external to the program, i.e. from files
> provided in RH's -debuginfo packages. 1
We've done that since 2.1.2 - it was bug #82872.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Nicholas N. <nj...@cs...> - 2005-11-21 17:01:27
|
On Mon, 21 Nov 2005, Tom Hughes wrote: > All looks pretty good to me. > >> - loading of debugging symbols external to the program, i.e. from files >> provided in RH's -debuginfo packages. 1 > > We've done that since 2.1.2 - it was bug #82872. Yes. There were a few responses like this where people didn't realise things (a couple of people suggested producing XML output, for example). I've mentioned a few of them in the release notes for 3.1.0. Nick |
|
From: Cerion Armour-B. <ce...@op...> - 2005-11-21 11:14:35
|
On Sunday 20 November 2005 21:11, Nicholas Nethercote wrote: > Hi, > > I've finally finished analysing the surveys. I attach two documents: > > 1. A high-level summary > 2. A detailed report > > I plan to put these up on the site and email the user list about it, but I > thought I'd run it past a few eyeballs before doing so. Let me know if > you see any mistakes or things that should be changed. Thanks. > > Nick Great stuff - lots of food for thought there! Couple of errors in 'report' line 856: spelling (laboriously, consequences) access and you don\'t have to laborously trace the bug back from the (sometimes very distant) place where the consequnces caused segfault. line 1181: missing words (will not be freed when the program exits) leak checking: there is some global or static object that will not freed when program exit, hope valgrind can detect this 1 And (being anal here) list items have a mix of starting caps and ending periods. Cerion |
|
From: Nicholas N. <nj...@cs...> - 2005-11-21 17:07:45
|
On Mon, 21 Nov 2005, Cerion Armour-Brown wrote: > Couple of errors in 'report' > > line 856: spelling (laboriously, consequences) > access and you don\'t have to laborously trace the bug back from the > (sometimes very distant) place where the consequnces caused segfault. > > line 1181: missing words (will not be freed when the program exits) > leak checking: there is some global or static object that will not freed > when program exit, hope valgrind can detect this 1 Right, I mostly didn't bother correcting typos from the responders. > And (being anal here) list items have a mix of starting caps and ending > periods. Send me a patch ;) I'll put the results on the website and announce to the other lists later. Nick |