4
0
mirror of git://sourceware.org/git/newlib-cygwin.git synced 2025-01-19 04:49:25 +08:00

Improve FAQ answer on debugging Cygwin

Improve FAQ answer on debugging Cygwin to mention the cygwin-debuginfo package
and the gdb command 'set cygwin-exceptions on'.

2015-08-03  Jon Turney  <jon.turney@dronecode.org.uk>

	* faq-programming.xml: Improve debugging-cygwin answer.

Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
This commit is contained in:
Jon TURNEY 2015-08-04 13:34:10 +01:00
parent 9698cc0f33
commit 49380b7ee3
2 changed files with 26 additions and 4 deletions

View File

@ -1,3 +1,7 @@
2015-08-03 Jon Turney <jon.turney@dronecode.org.uk>
* faq-programming.xml: Improve debugging-cygwin answer.
2015-07-21 Corinna Vinschen <corinna@vinschen.de> 2015-07-21 Corinna Vinschen <corinna@vinschen.de>
* new-features.xml (ov-new2.2): Document sigsetjmp, siglongjmp. * new-features.xml (ov-new2.2): Document sigsetjmp, siglongjmp.

View File

@ -747,14 +747,32 @@ same time. Remove all but one.
<question><para>I may have found a bug in Cygwin, how can I debug it (the symbols in gdb look funny)?</para></question> <question><para>I may have found a bug in Cygwin, how can I debug it (the symbols in gdb look funny)?</para></question>
<answer> <answer>
<para>Debugging symbols are stripped from distibuted Cygwin binaries, so any <para>Debugging symbols are stripped from distibuted Cygwin binaries, so to
symbols that you see in gdb are basically meaningless. It is also a good debug with <command>gdb</command> you will need to install the
<package>cygwin-debuginfo</package> package to obtain the debug symbols for
<filename>cygwin1.dll</filename>
</para>
<para>
If your bug causes an exception inside <filename>cygwin1.dll</filename> you will
need to use the <command>gdb</command> command <userinput>set cygwin-exceptions
on</userinput> to tell <command>gdb</command> to stop on exceptions inside the
Cygwin DLL (by default they are ignored, as they may be generated during normal
operation e.g. when checking a pointer is valid)
</para>
<para>
It is also a good
idea to use the latest code in case the bug has been fixed, so we idea to use the latest code in case the bug has been fixed, so we
recommend trying the latest snapshot from recommend trying the latest snapshot from
<ulink url="https://cygwin.com/snapshots/"/> or building the DLL from GIT. <ulink url="https://cygwin.com/snapshots/"/> or building the DLL from git.
</para> </para>
<para>To build a debugging version of the Cygwin DLL, you will need to follow <para>To build a debugging version of the Cygwin DLL, you will need to follow
the instructions at <ulink url="https://cygwin.com/faq/faq.html#faq.programming.building-cygwin"/>. the instructions at <ulink url="https://cygwin.com/faq/faq.html#faq.programming.building-cygwin"/>.
</para>
<para>
You can also contact the mailing list for pointers (a simple test case that You can also contact the mailing list for pointers (a simple test case that
demonstrates the bug is always welcome). demonstrates the bug is always welcome).
</para> </para>