http://bugs.winehq.org/show_bug.cgi?id=14368
Summary: enable more-robust debugging of signals and exceptions Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs@winehq.org ReportedBy: jreiser@BitWagon.com
Created an attachment (id=14665) --> (http://bugs.winehq.org/attachment.cgi?id=14665) ease debugging at lowest level of signals and exceptions
The code which handles signals and exceptions can be made more robust by using symbols for some bare numeric constants (EXCEPTION_WRITE_FAULT, EXCEPTION_EXECUTE_FAULT, EXCEPTION_READ_FAULT). Debugging can be made easier with a *printf() that uses only a few hundred bytes of stack space, in contrast to the several kilobytes required by the *printf() of glibc. With glibc it is too easy to overflow the stack of only 12 KiB. Patch is attached, and will be sent to wine-patches@winehq.org.
http://bugs.winehq.org/show_bug.cgi?id=14368
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
--- Comment #1 from Austin English austinenglish@gmail.com 2009-01-05 11:13:22 --- Is this still an issue in current (1.1.12 or newer) wine? Would you mind resubmitting the patch and asking for comments?
http://bugs.winehq.org/show_bug.cgi?id=14368
--- Comment #2 from Austin English austinenglish@gmail.com 2009-07-16 13:11:30 --- Still present.
http://bugs.winehq.org/show_bug.cgi?id=14368
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=14368
--- Comment #3 from Austin English austinenglish@gmail.com 2012-03-19 14:02:54 CDT --- Still present.
https://bugs.winehq.org/show_bug.cgi?id=14368
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
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... ).
https://bugs.winehq.org/show_bug.cgi?id=14368
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #5 from Austin English austinenglish@gmail.com --- (In reply to Sebastian Lackner from comment #4)
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#l2314 ).
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=14368
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Bruno Jesus 00cpxxx@gmail.com --- Closing abandoned bugs.
-
wine-bugs＠winehq.org