[Bug 51985] errors significance

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51985

--- Comment #7 from Didier <didu31 at hotmail.fr> ---
(In reply to Zebediah Figura from comment #6)
> The logs show that you have the "fsync" patch set applied to your Wine
> build. That's not part of upstream wine or wine-staging, regardless of what
> `wine --version` states.
> 
> (In reply to Didier from comment #5)
> > That's why I propose to add Fatal tag to the logs.
> > As the others softwares do.
> > A program is always able to tell what causes abort.
> > Just ask to the exception handler, for instance.
> 
> I don't think there's anything that could be meaningfully tagged as a fatal
> error. Broadly speaking, we *aren't* able to tell what caused an exception,
> only that one happened. It's a consequence of running code that we don't
> control and don't know the source of.

In case of windows software that decides to abort, it makes sense.
Ok, I understand your point of view.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.