From: Nikolay Molchanov <Nikolay.Molchanov@Sun.COM>
To: gdb@sourceware.org
Subject: Can I use -exec-interrupt to stop the inferior program?
Date: Mon, 15 May 2006 21:51:00 -0000 [thread overview]
Message-ID: <4468F31E.8090805@Sun.COM> (raw)
Hello!
I'm looking for a solution how to stop the inferior program,
which is running under gdb. I can stop it using ^C, but I
need a solution, that will work for the following case:
Java application
| ^
stdin | | stdout
v |
GDB debugger (gdb --i mi --tty /dev/pts/2 ...)
| ^
v |
Inferior program <--> External terminal (/dev/pts/28)
The action to stop the program is initiated by
Java application, which cannot send ^C to the
external terminal. So I have to use stdin to
tell gdb to stop the inferior program. But gdb
does not read the "-exec-interrupt" command,
until the program is stopped
sside-linux nikm/t1-exec-interrupt> gdb --i mi --tty /dev/pts/2 t2pl
~"GNU gdb 6.1\n"
~"Copyright 2004 Free Software Foundation, Inc.\n"
~"GDB is free software, covered by the GNU General Public License, and
you are\n"
~"welcome to change it and/or distribute copies of it under certain
conditions.\n"
~"Type \"show copying\" to see the conditions.\n"
~"There is absolutely no warranty for GDB. Type \"show warranty\" for
details.\n"
~"This GDB was configured as \"x86_64-suse-linux\"..."
~"Using host libthread_db library \"/lib64/tls/libthread_db.so.1\".\n"
~"\n"
(gdb)
run
&"run\n"
-exec-interrupt
^done,reason="exited",exit-code="0100"
(gdb)
^error,msg="mi_cmd_exec_interrupt: Inferior not executing."
(gdb)
Perhaps "-exec-interrupt" does not work in gdb 6.1?
If that's correct, can you tell me which version supports
"-exec-interrupt"?
Thanks in advance,
Nikolay Molchanov
next reply other threads:[~2006-05-15 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 21:51 Nikolay Molchanov [this message]
2006-05-16 11:35 ` Nick Roberts
2006-05-18 16:19 ` Carlos Eduardo Rodrigues de Almeida
2006-10-11 6:47 Nikolay Molchanov
2006-10-11 13:49 ` Daniel Jacobowitz
2006-10-11 17:32 ` Eli Zaretskii
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=4468F31E.8090805@Sun.COM \
--to=nikolay.molchanov@sun.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