[DOC] Interrupt when program is stopped

This patch changes the document that interrupt (ctrl-c) is not ignored
when the program is stopped.

When the interrupt was supported in remote target, people thought interrupt
is meaningless when the program is stopped.  See

  https://www.sourceware.org/ml/gdb/2005-11/msg00349.html
  https://www.sourceware.org/ml/gdb-patches/2005-11/msg00307.html

recently we find it is hard to preserve this feature "ignore interrupt
while program is stopped" when we fix some other bugs.  See
https://sourceware.org/ml/gdb-patches/2016-01/msg00039.html

so we think we can go to the simpler approach "not ignoring ctrl-c when
program is stopped".  As a result, we tweak the documentation here.

gdb/doc:

2016-01-12  Yao Qi  <yao.qi@linaro.org>

	* gdb.texinfo (Interrupts): Update the document on handling
	interrupt when program is stopped.
This commit is contained in:
Yao Qi 2016-01-12 14:59:45 +00:00
parent e46eeeddfb
commit cde67b27d6
2 changed files with 7 additions and 1 deletions

View file

@ -1,3 +1,8 @@
2016-01-12 Yao Qi <yao.qi@linaro.org>
* gdb.texinfo (Interrupts): Update the document on handling
interrupt when program is stopped.
2015-12-11 Don Breazeal <donb@codesourcery.com>
* gdb.texinfo (Forks): Correct Linux kernel version where

View file

@ -38130,7 +38130,8 @@ reply packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result
of successfully stopping the program in all-stop mode, and a stop reply
for each stopped thread in non-stop mode.
Interrupts received while the
program is stopped are discarded.
program is stopped are queued and the program will be interrupted when
it is resumed next time.
@node Notification Packets
@section Notification Packets