https://bugs.winehq.org/show_bug.cgi?id=14368
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- I think this bug can also be closed as abandoned. The code in its current form is not really useful. A lot of new functions are added, but not actually used. All the print/dump functions are commented out, and there seems to be no way to turn on this output at either compile time or runtime. Is the idea to have this code in place, so that developers can remove the comments manually in the wine source while trying to debug Valgrind related issues? It is unlikely that such a change will ever get upstream. Moreover no response from author since 7 years.
If there is a need for enhanced traces / debugging while executing the signal handler, it should make use of the existing wine TRACE / FIXME / ... functions, or at least allow to enable/disable it at runtime using debug channels. If the signal stack is not big enough for specific purposes, it can be easily increased by adjusting "min_size" or "sigstack_zero_bits" ( http://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ntdll/signal_i386.c#l2... ).