Hi Philipp,
> Still i want to
> be able to see from the title what an issue is generally about. A tool
> can never know that, so at least the valgrind title tells me what class
> of issues this belongs to.
Okay, that's a point.
>>Do Valgrind bugs really have an ID? (I mean, except the issue ID)?
>>Aren't they defined by a test case, not by an ID?
>
> "Die normative Kraft des Faktischen" ist da am Werk. Already existing
> tasks tell us that currently they have an ID.
I'd be interested what the information of this ID is, except "it's the
n'th Valgrind issue ever submitted", which would make it useless.
>>I suggest having the "Error type" or "Error text" (which according to
>>the Wiki are in the issue description) as summary, since this better
>>describes what's going on than "Valgrind ID:x". We could enhance this
>>with the file name where the error occurs, or things like this.
>>Everything allows you to grasp an idea of the issue just from reading
>>the summary.
>
> This would be what ? There is no direct relation between any test case
> basic line and the valgrind output AFAIK, what would be the "Error text"
> in your opinion ?
Looking at an arbitrary example (internal issue 134294, really picked
randomly): Wouldn't you cosider
"Invalid read of size 4" in Application::GetSolarMutex
consider a better summary than
Valgrind ID: 16
I definately do.
I'm pretty sure that the number of possible Valgrind error texts is
short enought that people might learn to recognize Valgrind issues just
by those texts ("Invalid read ..." etc.) in the summary, but to ease the
recognition, it might in fact be helpful to have
[Valgrind] "Invalid read of size 4" in Application::GetSolarMutex
or so. I still think it would not be necessary on the long run, and
duplicates information found elsewhere (in the keywords), but be it.
(Yes, I shifted my point from "do not use Valgrind in the summary 'cause
..." to "Provide a meaningful summary" [1] :). )
Ciao
Frank
[1] http://qa.openoffice.org/issue_handling/basic_rules.html#summary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
