From: teawater <teawater@gmail.com>
To: Sushrut Sardeshmukh <bestbrain@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: SIGINT sent to executable
Date: Mon, 02 Feb 2009 07:06:00 -0000 [thread overview]
Message-ID: <daef60380902012306x21763402t36750bfe832b50f6@mail.gmail.com> (raw)
In-Reply-To: <f0ef23030901312018g900af95lb5326ece70995612@mail.gmail.com>
I think this is because
> Signal Stop Print Pass to program Description
SIGINT Yes Yes No Interrupt
Stop mean that when inferior get a sigint, gdb will stop the inferior.
I think you can try to use command "handle" to set it to "No".
Thanks,
Hui
On Sun, Feb 1, 2009 at 12:18, Sushrut Sardeshmukh <bestbrain@gmail.com> wrote:
> I searched google before sending this email. But could not find the
> solution to the problem :(
>
> I am using ddd+gdb on Linux to debug executable which handles SIGINT
> to do graceful shutdown.
>
> gdb is set not to pass SIGINT to executable.
> (gdb) info signal
> Signal Stop Print Pass to program Description
> SIGHUP Yes Yes Yes Hangup
> SIGINT Yes Yes No Interrupt
>
> However, when I press Interrupt button in ddd, executable gets SIGINT
> and it does graceful shutdown. Totalview debugger is able to interrupt
> execution. So it must be something wrong with the way I am setting up
> gdb.
>
> How can I interrupt the execution and get gdb prompt (to set another
> breapoint/ watchpoint) but not send SIGINT to executable ?
>
>
> Here is version info about gdb
> gdb --version
> GNU gdb 6.8
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/
> gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show
> copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
>
prev parent reply other threads:[~2009-02-02 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 4:18 Sushrut Sardeshmukh
2009-02-02 7:06 ` teawater [this message]
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=daef60380902012306x21763402t36750bfe832b50f6@mail.gmail.com \
--to=teawater@gmail.com \
--cc=bestbrain@gmail.com \
--cc=gdb@sourceware.org \
/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