From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
Subject: Re: Looks like GDB in Cygwin does not catch Ctrl/C correctly
Date: Tue, 21 Jan 2020 03:16:00 -0000 [thread overview]
Message-ID: <20200121121557.9260057468bdfee5896273dc@nifty.ne.jp> (raw)
In-Reply-To: <SN6PR09MB2877244888717FA8ADE4EE31A50D0@SN6PR09MB2877.namprd09.prod.outlook.com>
On Tue, 21 Jan 2020 03:09:19 +0000
"Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" <cygwin@cygwin.com> wrote:
> Hi All,
>
> Another question for tonight:
>
> So there's a program that basically enters a tight loop on some incorrect input (and needs to be debugged, obviously).
>
> The program is otherwise rather basic, doesn't use anything outside K&R C RTL.
>
> When I run the program under gdb, I want to interrupt it with Ctrl/C (as I would be doing
> in Linux) and then step through the code to figure out where it is looping.
>
> GDB does interrupt the program but when I do step or next, it looks like some
> utility thread gets the actual control, and actually processes the INT signal, which then
> terminates the program, making the debugging impossible:
>
> Thread 1 "cprog" received signal SIGINT, Interrupt.
> free_tree (tp=0x80004eae0) at cprog.c:1696
> 1696 break;
> (gdb) s
> 0x0000000180148990 in muto::release(_cygtls*) () from /usr/bin/cygwin1.dll
> (gdb) s
> Single stepping until exit from function _ZN4muto7releaseEP7_cygtls,
> which has no line number information.
> 0x000000018013469b in _sigbe () from /usr/bin/cygwin1.dll
> (gdb) s
> Single stepping until exit from function _sigbe,
> which has no line number information.
> 0x00000001801346e5 in sigdelayed () from /usr/bin/cygwin1.dll
> (gdb) s
> Single stepping until exit from function sigdelayed,
> which has no line number information.
> [Inferior 1 (process 6792) exited with code 01000]
>
> Using "n" instead of "s"s gets the termination right away:
>
> (gdb) n
> [Inferior 1 (process 5020) exited with code 01000]
>
> The program does have all the debugging info on (compiled with -g)
> and can be stepped through successfully (in Cygwin too from the get go but not whe interrupted).
>
> The same code compiled with the exact same gcc command, and run under gdb on Linux can be stepped through the actual
> source code after having been interrupted with Ctrl/C.
>
> Any ideas would be appreciated.
>
> Thanks,
> Anton
>
> P.S. This is how the debugging session looks on Linux, for comparison, showing it does step through the actual code:
>
> Program received signal SIGINT, Interrupt.
> 0x00000000004053f1 in implicit_gbl (value=0x6269f0) at cprog.c:2494
> 2494 switch(value->type)
> (gdb) n
> 2527 }
> (gdb) n
> store_value (stack=0x7fffffffc718, tr=0x7fffffffc720, size=1, value=0x6269f0) at cprog.c:3805
> 3805 if(value->type == EX_LIT)
> (gdb) n
> 3807 store_word(stack->top, tr, size, value->data.lit);
> (gdb)
> ...
What is your environment? Windows version, cygwin version and etc...
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-01-21 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 3:09 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 3:16 ` Takashi Yano [this message]
2020-01-21 3:29 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 3:57 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200121121557.9260057468bdfee5896273dc@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=lavr@ncbi.nlm.nih.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).