Mail Archives: cygwin/2006/07/24/16:19:58
I think problem reports in itself are already useful so people can
search the mailing lists to see whether the type of problem they run
into is already reported. With some luck they can solve or workaround it
with the suggestions, but even if no solution or explanation is
available, it may save quite some effort while trying to figure out
whether the problem is just caused by yourself, e.g. by ignorance or
that other people ran into the same issue. (In this particular case,
someone could upgrade the Cygwin installation for a very different
reason and all of a sudden been bitten by the difference in make
behavior.)
> -----Original Message-----
> Sent: Monday, July 24, 2006 9:53 PM
> Christopher Faylor wrote:
>
> > Well, you *could* expect a fix if you provided enough details.
>
> Understood. The question is, can there still be value in reporting
that a
> program crashes, even with minimal but potentially still useful
> information? I'm just asking and am genuinely interested in hearing
the
> developers' preferences. My choice in this case ("threadlist_ix -1")
was
> either to do nothing (for reasons not directly relevant to this
> discussion)
> or to post the information I had (the fact that it crashes and the
> associated error message). If this kind of less-than-ideal problem
report
> is considered to be always useless, which would come as a surprise to
me
> because as a developer I've seen many cases where a report like this
is
> all
> that was needed to highlight the problem, then I won't post anything
to
> this list in the future unless I have the resources to produce a
complete,
> easily reproducible bug report.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -