wine-1.5.20 reversion compared to 1.5.19 and previous; MinGW/gcc 4.7.0 segfaults under wineconsole

[Frédéric Delanoy]

On Mon, Dec 24, 2012 at 8:58 AM, Alan W. Irwin
<irwin at beluga.phys.uvic.ca> wrote:
> On 2012-12-23 21:25-0600 Austin English wrote:
>
>> On Dec 23, 2012 7:22 PM, "Alan W. Irwin" <irwin at beluga.phys.uvic.ca>
>> wrote:
>>>
>>> The subject line pretty much says it all.  Running MinGW/gcc under
>>> wineconsole for any simple test programme should demonstrate the issue
>>> for wine-1.5.20 which is not present in wine-1.5.19 and a fairly large
>>> selection of 1.5.x and MinGW versions I have tried over the last year
>>> or so.
>>>
>>> I would be happy to supply more details if there is any difficulty
>>> replicating this reversion.
>>>
>>> Alan
>>
>> Please run a regression test and file a bug at http://bugs.winehq.org.
>
> No thank you.

Why would anyone help you if you fail to do your homework? Your bug
description is rather vague and you can't expect people to start
randomly testing apps until they (supposedly) find the bug you're
talking about. Please provide a minimal  "simple test program"
If you want it fixed, failing to cooperate here won't help you much.
Instead, create your test program, specify download links, and
describe a minimal procedure to reproduce your bug (and add the
appropriate keywords: download, patch, testcase, ...)

http://wiki.winehq.org/BugReports and
http://bugs.winehq.org/describekeywords.cgi can help here.

For regressions, especially a rather recent one like you seem to
suggest, there are more likely to be fixed quickly, especially if you
perform the regression test yourself (reasons: you're in the best
position to do it yourself; it can take some time developpers won't
necessarily have: if they ran regression tests all day, when would
they code???)
See http://wiki.winehq.org/RegressionTesting

> The last time I wrote a wine bug report (with a test case and a patch
> to fix the problem no less),

Which bug?
> wine developers seemed content with the
> fact that that bug had been reported.  They did not actually fix the
> problem until I made a special personal appeal to one of them more
> than a year later. So eventually there was a happy ending there, but
> the impression I got from that experience is that Wine bug reports for
> even the most obvious issues like that one are pretty much a waste of
> everyone's time unless and until a Wine developer takes
> responsibility.  Of course, in that case the bug reporting system is
> worthwhile since it can make a permanent record of all the events
> leading to a solution.

If the bug was trivial to fix, why did you not send it yourself to wine-patches?
There are a lot of bugs, and not many people who can fix those, so you
can't expect *your* bug to be fixed in minutes.
If you want to increase your chance for the bug to be fixed, you could
wait less than a year, and e.g. restest if the bug still persists
every couple of months (or better, after every wine release) and tell
so on the bug report.

No amount of complaining on this list will likely help...

> In this case, I would like a Wine developer to take responsibility as
> well for what I think is an obvious issue with 1.5.20 by verifying the
> issue, and then taking any further development steps they want to take
> concerning this issue.  Or perhaps there will be an even more obvious
> symptom of the problem with 1.5.20 that will lead to a solution
> quicker than if someone follows the MinGW segfault symptom that I have
> found.  In other words, I am willing to help out Wine by reporting the
> issue informally here, and let Wine developers make their best
> judgement of what to do about the issue, but that is about it.

Again, the bugzilla system is there to report bug, not this mailing list.
Do you really expect someone to read your mail and create a bug from it???

> Sorry I have to be ruthless about this, but I do not want to get
> involved in wine development or go through a bunch of Wine
> bug-reporting hoops since I need to reserve my development efforts for
> my own free software projects.

If you don't want to be cooperative, why should we help you???
Creating a good bug report is not really "being involved in wine
development" IMO. Mere users without any programming experience do it
regularly.
>
> Alan

Frédéric