Currently, if a probe fails, it will print the line number of the [test]
block the probe is in, not the line number of the probe itself. This
makes it somewhat difficult to debug.
This commit makes it print the line number of the probe as well.
CC @zfigura
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/499
On Mon Nov 27 20:35:08 2023 +0000, Gabriel Ivăncescu wrote:
> Yeah. As I said below, I can easily just get rid of the tests and do the
> right thing with a comment. Silently dropping events sounds like a bad
> idea to me, it will make it hard to debug if something broken ever
> depends on it. And it's not like it's more code, either, so better make
> it correct.
My guess is that you wouldn't be able to reproduce that with JS. If that's the case, then web pages can't depend on that (otherwise we'd have a way to crash web browser from JS).
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4380#note_53978
> As for the "hide problems in the future", I actually think the exact opposite. Right now, we use the document's outer_window in same way, except it's completely broken and can access invalid memory if the outer window happens to die, which would be very hard to debug (especially considering most apps using mshtml are bloated and slow with millions of frameworks).
Yes, it would be nice to fix that. One fix for that is to simply reset the pointer to NULL. My understanding is that the actual reason we can't do that is iframe navigation test and we already know that the test works because on native, the document interface doesn't change. So what you do is essentially working around that problem, not fixing it.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4380#note_53977