Pass Ctrl-C to the target in target_terminal_inferior

[deliverable/binutils-gdb.git] / gdb / README

diff --git a/gdb/README b/gdb/README
index 999f9927f6c4a3a6fb2b27308ccb0f0613443a7f..d485536ecfe30667cb7b9a28172a46fa9aef0a16 100644 (file)
--- a/gdb/README
+++ b/gdb/README
@@ -446,10 +446,10 @@ prefer; but you may abbreviate option names if you use `--'.
      Build GDB with the gdbtk GUI interface.  Requires TCL/Tk to be
      installed.
 
-`--with-libunwind'
-     Use the libunwind library for unwinding function call stack.  See
-     http://www.nongnu.org/libunwind/index.html fro details.
-     Supported only on some platforms.
+`--with-libunwind-ia64'
+     Use the libunwind library for unwinding function call stack on ia64
+     target platforms.
+     See http://www.nongnu.org/libunwind/index.html for details.
 
 `--with-curses'
      Use the curses library instead of the termcap library, for
@@ -577,15 +577,16 @@ try typing `M-x gdb RET'.
 Writing Code for GDB
 =====================
 
-   There is a lot of information about writing code for GDB in the
-internals manual, distributed with GDB in gdb/doc/gdbint.texinfo.  You
-can read it by hand, print it by using TeX and texinfo, or process it
-into an `info' file for use with Emacs' info mode or the standalone
-`info' program.
+   There is information about writing code for GDB in the file
+`CONTRIBUTE' and at the website:
+
+       http://www.gnu.org/software/gdb/
+
+in particular in the wiki.
 
    If you are pondering writing anything but a short patch, especially
-take note of the information about copyrights in the node Submitting
-Patches.  It can take quite a while to get all the paperwork done, so
+take note of the information about copyrights and copyright assignment.
+It can take quite a while to get all the paperwork done, so
 we encourage you to start that process as soon as you decide you are
 planning to work on something, or at least well ahead of when you
 think you will be ready to submit the patches.