* [PATCH] Update FAQ question and answer about gdb and signals
@ 2016-01-14 18:05 Jon Turney
2016-01-14 19:50 ` Corinna Vinschen
0 siblings, 1 reply; 2+ messages in thread
From: Jon Turney @ 2016-01-14 18:05 UTC (permalink / raw)
To: cygwin-patches; +Cc: Jon Turney
Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>
---
winsup/doc/faq-programming.xml | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
index af6102a..7f1ffd9 100644
--- a/winsup/doc/faq-programming.xml
+++ b/winsup/doc/faq-programming.xml
@@ -859,15 +859,22 @@ on using <literal>strace</literal>, see the Cygwin User's Guide.
</answer></qandaentry>
<qandaentry id="faq.programming.gdb-signals">
-<question><para>Why doesn't gdb handle signals?</para></question>
+<question><para>How does gdb handle signals?</para></question>
<answer>
-<para>Unfortunately, there is only minimal signal handling support in gdb
-currently. Signal handling only works with Windows-type signals.
-SIGINT may work, SIGFPE may work, SIGSEGV definitely does. You cannot
-'stop', 'print' or 'nopass' signals like SIGUSR1 or SIGHUP to the
-process being debugged.
+<para>
+gdb maps known Windows exceptions to signals such as SIGSEGV, SIGFPE, SIGTRAP,
+SIGINT and SIGILL. Other Windows exceptions are passed on to the handler (if
+any), and reported as an unknown signal if an unhandled (second chance)
+exception occurs.
</para>
+
+<para>
+There is also an experimental feature to notify gdb of purely Cygwin signals
+like SIGABRT, SIGHUP or SIGUSR1. This currently has some known problems, for
+example, single-stepping from these signals may not work as expected.
+</para>
+
</answer></qandaentry>
<qandaentry id="faq.programming.linker">
--
2.6.2
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Update FAQ question and answer about gdb and signals
2016-01-14 18:05 [PATCH] Update FAQ question and answer about gdb and signals Jon Turney
@ 2016-01-14 19:50 ` Corinna Vinschen
0 siblings, 0 replies; 2+ messages in thread
From: Corinna Vinschen @ 2016-01-14 19:50 UTC (permalink / raw)
To: cygwin-patches
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
On Jan 14 18:05, Jon Turney wrote:
> Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>
> ---
> winsup/doc/faq-programming.xml | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
> index af6102a..7f1ffd9 100644
> --- a/winsup/doc/faq-programming.xml
> +++ b/winsup/doc/faq-programming.xml
> @@ -859,15 +859,22 @@ on using <literal>strace</literal>, see the Cygwin User's Guide.
> </answer></qandaentry>
>
> <qandaentry id="faq.programming.gdb-signals">
> -<question><para>Why doesn't gdb handle signals?</para></question>
> +<question><para>How does gdb handle signals?</para></question>
> <answer>
>
> -<para>Unfortunately, there is only minimal signal handling support in gdb
> -currently. Signal handling only works with Windows-type signals.
> -SIGINT may work, SIGFPE may work, SIGSEGV definitely does. You cannot
> -'stop', 'print' or 'nopass' signals like SIGUSR1 or SIGHUP to the
> -process being debugged.
> +<para>
> +gdb maps known Windows exceptions to signals such as SIGSEGV, SIGFPE, SIGTRAP,
> +SIGINT and SIGILL. Other Windows exceptions are passed on to the handler (if
> +any), and reported as an unknown signal if an unhandled (second chance)
> +exception occurs.
> </para>
> +
> +<para>
> +There is also an experimental feature to notify gdb of purely Cygwin signals
> +like SIGABRT, SIGHUP or SIGUSR1. This currently has some known problems, for
> +example, single-stepping from these signals may not work as expected.
> +</para>
> +
> </answer></qandaentry>
>
> <qandaentry id="faq.programming.linker">
> --
> 2.6.2
ACK
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-01-14 19:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-14 18:05 [PATCH] Update FAQ question and answer about gdb and signals Jon Turney
2016-01-14 19:50 ` Corinna Vinschen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).