* Minor fix to comment in "minsyms.c"
@ 2000-04-18 18:33 Guy Harris
2000-04-19 14:13 ` Jim Blandy
0 siblings, 1 reply; 2+ messages in thread
From: Guy Harris @ 2000-04-18 18:33 UTC (permalink / raw)
To: gdb-patches
"I see no MSYMBOL_HASH_ADD here." One version of the minsyms hashing
patch had that macro, but the code in the CVS tree has the
"add_minsym_to_hash_table()" function instead.
*** /u/guy/src/cmd/gdb-cygnus-cvs/gdb/minsyms.c Tue Apr 18 17:35:37 2000
--- ./minsyms.c Tue Apr 18 17:55:52 2000
***************
*** 685,691 ****
MSYMBOL_INFO (msymbol) = info; /* FIXME! */
/* The hash pointers must be cleared! If they're not,
! MSYMBOL_HASH_ADD will NOT add this msymbol to the hash table. */
msymbol->hash_next = NULL;
msymbol->demangled_hash_next = NULL;
--- 685,691 ----
MSYMBOL_INFO (msymbol) = info; /* FIXME! */
/* The hash pointers must be cleared! If they're not,
! add_minsym_to_hash_table will NOT add this msymbol to the hash table. */
msymbol->hash_next = NULL;
msymbol->demangled_hash_next = NULL;
From ac131313@cygnus.com Tue Apr 18 18:58:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH/5] Remove stray (?) readline file
Date: Tue, 18 Apr 2000 18:58:00 -0000
Message-id: <38FD1276.E5BE1928@cygnus.com>
X-SW-Source: 2000-04/msg00358.html
Content-length: 54912
FYI,
I've committed the attatched. The generated man page is removed by
distclean and generated by the Makefile. of course the next readline
import could change all that.
Andrew
Tue Apr 18 15:43:52 2000 Andrew Cagney <cagney@b1.cygnus.com>
* readline.0: Delete. Generated by Makefile, deleted by distclean
rule.
Index: readline.0
===================================================================
RCS file: readline.0
diff -N readline.0
*** /sourceware/cvs-tmp/cvsGQgBVZ Tue Apr 18 18:54:32 2000
--- /dev/null Tue May 5 13:32:27 1998
***************
*** 1,1188 ****
-
-
-
- READLINE(3) READLINE(3)
-
-
- N\bNA\bAM\bME\bE
- readline - get a line from a user with editing
-
- S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
- #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<s\bst\btd\bdi\bio\bo.\b.h\bh>\b>
- #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<r\bre\bea\bad\bdl\bli\bin\bne\be.\b.h\bh>\b>
- #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<h\bhi\bis\bst\bto\bor\bry\by.\b.h\bh>\b>
-
- c\bch\bha\bar\br *\b*r\bre\bea\bad\bdl\bli\bin\bne\be (\b(p\bpr\bro\bom\bmp\bpt\bt)\b)
- c\bch\bha\bar\br *\b*p\bpr\bro\bom\bmp\bpt\bt;\b;
-
- C\bCO\bOP\bPY\bYR\bRI\bIG\bGH\bHT\bT
- Readline is Copyright (C) 1989, 1991, 1993, 1995, 1996 by
- the Free Software Foundation, Inc.
-
- D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- r\bre\bea\bad\bdl\bli\bin\bne\be will read a line from the terminal and return it,
- using p\bpr\bro\bom\bmp\bpt\bt as a prompt. If p\bpr\bro\bom\bmp\bpt\bt is null, no prompt is
- issued. The line returned is allocated with _\bm_\ba_\bl_\bl_\bo_\bc(3), so
- the caller must free it when finished. The line returned
- has the final newline removed, so only the text of the
- line remains.
-
- r\bre\bea\bad\bdl\bli\bin\bne\be offers editing capabilities while the user is
- entering the line. By default, the line editing commands
- are similar to those of emacs. A vi-style line editing
- interface is also available.
-
- R\bRE\bET\bTU\bUR\bRN\bN V\bVA\bAL\bLU\bUE\bE
- r\bre\bea\bad\bdl\bli\bin\bne\be returns the text of the line read. A blank line
- returns the empty string. If E\bEO\bOF\bF is encountered while
- reading a line, and the line is empty, N\bNU\bUL\bLL\bL is returned.
- If an E\bEO\bOF\bF is read with a non-empty line, it is treated as
- a newline.
-
- N\bNO\bOT\bTA\bAT\bTI\bIO\bON\bN
- An emacs-style notation is used to denote keystrokes.
- Control keys are denoted by C-_\bk_\be_\by, e.g., C-n means Con-
- trol-N. Similarly, _\bm_\be_\bt_\ba keys are denoted by M-_\bk_\be_\by, so M-x
- means Meta-X. (On keyboards without a _\bm_\be_\bt_\ba key, M-_\bx means
- ESC _\bx, i.e., press the Escape key then the _\bx key. This
- makes ESC the _\bm_\be_\bt_\ba _\bp_\br_\be_\bf_\bi_\bx. The combination M-C-_\bx means
- ESC-Control-_\bx, or press the Escape key then hold the Con-
- trol key while pressing the _\bx key.)
-
- Readline commands may be given numeric _\ba_\br_\bg_\bu_\bm_\be_\bn_\bt_\bs, which
- normally act as a repeat count. Sometimes, however, it is
- the sign of the argument that is significant. Passing a
- negative argument to a command that acts in the forward
- direction (e.g., k\bki\bil\bll\bl-\b-l\bli\bin\bne\be) causes that command to act in
- a backward direction. Commands whose behavior with argu-
- ments deviates from this are noted.
-
- When a command is described as _\bk_\bi_\bl_\bl_\bi_\bn_\bg text, the text
-
-
-
- GNU 1998 Dec 31 1
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- deleted is saved for possible future retrieval (_\by_\ba_\bn_\bk_\bi_\bn_\bg).
- The killed text is saved in a _\bk_\bi_\bl_\bl _\br_\bi_\bn_\bg. Consecutive
- kills cause the text to be accumulated into one unit,
- which can be yanked all at once. Commands which do not
- kill text separate the chunks of text on the kill ring.
-
- I\bIN\bNI\bIT\bTI\bIA\bAL\bLI\bIZ\bZA\bAT\bTI\bIO\bON\bN F\bFI\bIL\bLE\bE
- Readline is customized by putting commands in an initial-
- ization file (the _\bi_\bn_\bp_\bu_\bt_\br_\bc file). The name of this file is
- taken from the value of the I\bIN\bNP\bPU\bUT\bTR\bRC\bC environment variable.
- If that variable is unset, the default is _\b~_\b/_\b._\bi_\bn_\bp_\bu_\bt_\br_\bc.
- When a program which uses the readline library starts up,
- the init file is read, and the key bindings and variables
- are set. There are only a few basic constructs allowed in
- the readline init file. Blank lines are ignored. Lines
- beginning with a #\b# are comments. Lines beginning with a $\b$
- indicate conditional constructs. Other lines denote key
- bindings and variable settings. Each program using this
- library may add its own commands and bindings.
-
- For example, placing
-
- M-Control-u: universal-argument
- or
- C-Meta-u: universal-argument
- into the _\bi_\bn_\bp_\bu_\bt_\br_\bc would make M-C-u execute the readline
- command _\bu_\bn_\bi_\bv_\be_\br_\bs_\ba_\bl_\b-_\ba_\br_\bg_\bu_\bm_\be_\bn_\bt.
-
- The following symbolic character names are recognized
- while processing key bindings: _\bR_\bU_\bB_\bO_\bU_\bT, _\bD_\bE_\bL, _\bE_\bS_\bC, _\bL_\bF_\bD, _\bN_\bE_\bW_\b-
- _\bL_\bI_\bN_\bE, _\bR_\bE_\bT, _\bR_\bE_\bT_\bU_\bR_\bN, _\bS_\bP_\bC, _\bS_\bP_\bA_\bC_\bE, and _\bT_\bA_\bB. In addition to
- command names, readline allows keys to be bound to a
- string that is inserted when the key is pressed (a _\bm_\ba_\bc_\br_\bo).
-
-
- K\bKe\bey\by B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
- The syntax for controlling key bindings in the _\bi_\bn_\bp_\bu_\bt_\br_\bc
- file is simple. All that is required is the name of the
- command or the text of a macro and a key sequence to which
- it should be bound. The name may be specified in one of
- two ways: as a symbolic key name, possibly with _\bM_\be_\bt_\ba_\b- or
- _\bC_\bo_\bn_\bt_\br_\bo_\bl_\b- prefixes, or as a key sequence. When using the
- form k\bke\bey\byn\bna\bam\bme\be:_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b-_\bn_\ba_\bm_\be or _\bm_\ba_\bc_\br_\bo, _\bk_\be_\by_\bn_\ba_\bm_\be is the name
- of a key spelled out in English. For example:
-
- Control-u: universal-argument
- Meta-Rubout: backward-kill-word
- Control-o: ">&output"
-
- In the above example, _\bC_\b-_\bu is bound to the function u\bun\bni\biv\bve\ber\br-\b-
- s\bsa\bal\bl-\b-a\bar\brg\bgu\bum\bme\ben\bnt\bt, _\bM_\b-_\bD_\bE_\bL is bound to the function b\bba\bac\bck\bk-\b-
- w\bwa\bar\brd\bd-\b-k\bki\bil\bll\bl-\b-w\bwo\bor\brd\bd, and _\bC_\b-_\bo is bound to run the macro
- expressed on the right hand side (that is, to insert the
- text _\b>_\b&_\bo_\bu_\bt_\bp_\bu_\bt into the line).
-
-
-
- GNU 1998 Dec 31 2
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- In the second form, "\b"k\bke\bey\bys\bse\beq\bq"\b":_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b-_\bn_\ba_\bm_\be or _\bm_\ba_\bc_\br_\bo, k\bke\bey\by-\b-
- s\bse\beq\bq differs from k\bke\bey\byn\bna\bam\bme\be above in that strings denoting an
- entire key sequence may be specified by placing the
- sequence within double quotes. Some GNU Emacs style key
- escapes can be used, as in the following example.
-
- "\C-u": universal-argument
- "\C-x\C-r": re-read-init-file
- "\e[11~": "Function Key 1"
-
- In this example, _\bC_\b-_\bu is again bound to the function u\bun\bni\bi-\b-
- v\bve\ber\brs\bsa\bal\bl-\b-a\bar\brg\bgu\bum\bme\ben\bnt\bt. _\bC_\b-_\bx _\bC_\b-_\br is bound to the function
- r\bre\be-\b-r\bre\bea\bad\bd-\b-i\bin\bni\bit\bt-\b-f\bfi\bil\ble\be, and _\bE_\bS_\bC _\b[ _\b1 _\b1 _\b~ is bound to insert the
- text F\bFu\bun\bnc\bct\bti\bio\bon\bn K\bKe\bey\by 1\b1. The full set of GNU Emacs style
- escape sequences is
- \\b\C\bC-\b- control prefix
- \\b\M\bM-\b- meta prefix
- \\b\e\be an escape character
- \\b\\\b\ backslash
- \\b\"\b" literal "
- \\b\'\b' literal '
-
- In addition to the GNU Emacs style escape sequences, a
- second set of backslash escapes is available:
- \\b\a\ba alert (bell)
- \\b\b\bb backspace
- \\b\d\bd delete
- \\b\f\bf form feed
- \\b\n\bn newline
- \\b\r\br carriage return
- \\b\t\bt horizontal tab
- \\b\v\bv vertical tab
- \\b\_\bn_\bn_\bn the character whose ASCII code is the octal
- value _\bn_\bn_\bn (one to three digits)
- \\b\x\bx_\bn_\bn_\bn the character whose ASCII code is the hex-
- adecimal value _\bn_\bn_\bn (one to three digits)
-
- When entering the text of a macro, single or double quotes
- should be used to indicate a macro definition. Unquoted
- text is assumed to be a function name. In the macro body,
- the backslash escapes described above are expanded. Back-
- slash will quote any other character in the macro text,
- including " and '.
-
- B\bBa\bas\bsh\bh allows the current readline key bindings to be dis-
- played or modified with the b\bbi\bin\bnd\bd builtin command. The
- editing mode may be switched during interactive use by
- using the -\b-o\bo option to the s\bse\bet\bt builtin command. Other
- programs using this library provide similar mechanisms.
- The _\bi_\bn_\bp_\bu_\bt_\br_\bc file may be edited and re-read if a program
- does not provide any other means to incorporate new bind-
- ings.
-
-
-
-
-
- GNU 1998 Dec 31 3
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
- Readline has variables that can be used to further cus-
- tomize its behavior. A variable may be set in the _\bi_\bn_\bp_\bu_\bt_\br_\bc
- file with a statement of the form
-
- s\bse\bet\bt _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b-_\bn_\ba_\bm_\be _\bv_\ba_\bl_\bu_\be
-
- Except where noted, readline variables can take the values
- O\bOn\bn or O\bOf\bff\bf. The variables and their default values are:
-
- b\bbe\bel\bll\bl-\b-s\bst\bty\byl\ble\be (\b(a\bau\bud\bdi\bib\bbl\ble\be)\b)
- Controls what happens when readline wants to ring
- the terminal bell. If set to n\bno\bon\bne\be, readline never
- rings the bell. If set to v\bvi\bis\bsi\bib\bbl\ble\be, readline uses a
- visible bell if one is available. If set to a\bau\bud\bdi\bi-\b-
- b\bbl\ble\be, readline attempts to ring the terminal's bell.
- c\bco\bom\bmm\bme\ben\bnt\bt-\b-b\bbe\beg\bgi\bin\bn (\b(`\b``\b`#\b#'\b''\b')\b)
- The string that is inserted in v\bvi\bi mode when the
- i\bin\bns\bse\ber\brt\bt-\b-c\bco\bom\bmm\bme\ben\bnt\bt command is executed. This command
- is bound to M\bM-\b-#\b# in emacs mode and to #\b# in vi com-
- mand mode.
- c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bn-\b-i\big\bgn\bno\bor\bre\be-\b-c\bca\bas\bse\be (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, readline performs filename matching
- and completion in a case-insensitive fashion.
- c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bn-\b-q\bqu\bue\ber\bry\by-\b-i\bit\bte\bem\bms\bs (\b(1\b10\b00\b0)\b)
- This determines when the user is queried about
- viewing the number of possible completions gener-
- ated by the p\bpo\bos\bss\bsi\bib\bbl\ble\be-\b-c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bns\bs command. It may
- be set to any integer value greater than or equal
- to zero. If the number of possible completions is
- greater than or equal to the value of this vari-
- able, the user is asked whether or not he wishes to
- view them; otherwise they are simply listed on the
- terminal.
- c\bco\bon\bnv\bve\ber\brt\bt-\b-m\bme\bet\bta\ba (\b(O\bOn\bn)\b)
- If set to O\bOn\bn, readline will convert characters with
- the eighth bit set to an ASCII key sequence by
- stripping the eighth bit and prepending an escape
- character (in effect, using escape as the _\bm_\be_\bt_\ba _\bp_\br_\be_\b-
- _\bf_\bi_\bx).
- d\bdi\bis\bsa\bab\bbl\ble\be-\b-c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bn (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, readline will inhibit word comple-
- tion. Completion characters will be inserted into
- the line as if they had been mapped to s\bse\bel\blf\bf-\b-i\bin\bns\bse\ber\brt\bt.
- e\bed\bdi\bit\bti\bin\bng\bg-\b-m\bmo\bod\bde\be (\b(e\bem\bma\bac\bcs\bs)\b)
- Controls whether readline begins with a set of key
- bindings similar to _\be_\bm_\ba_\bc_\bs or _\bv_\bi. e\bed\bdi\bit\bti\bin\bng\bg-\b-m\bmo\bod\bde\be can
- be set to either e\bem\bma\bac\bcs\bs or v\bvi\bi.
- e\ben\bna\bab\bbl\ble\be-\b-k\bke\bey\byp\bpa\bad\bd (\b(O\bOf\bff\bf)\b)
- When set to O\bOn\bn, readline will try to enable the
- application keypad when it is called. Some systems
- need this to enable the arrow keys.
- e\bex\bxp\bpa\ban\bnd\bd-\b-t\bti\bil\bld\bde\be (\b(O\bOf\bff\bf)\b)
- If set to o\bon\bn, tilde expansion is performed when
-
-
-
- GNU 1998 Dec 31 4
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- readline attempts word completion.
- h\bho\bor\bri\biz\bzo\bon\bnt\bta\bal\bl-\b-s\bsc\bcr\bro\bol\bll\bl-\b-m\bmo\bod\bde\be (\b(O\bOf\bff\bf)\b)
- When set to O\bOn\bn, makes readline use a single line
- for display, scrolling the input horizontally on a
- single screen line when it becomes longer than the
- screen width rather than wrapping to a new line.
- i\bin\bnp\bpu\but\bt-\b-m\bme\bet\bta\ba (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, readline will enable eight-bit input
- (that is, it will not strip the high bit from the
- characters it reads), regardless of what the termi-
- nal claims it can support. The name m\bme\bet\bta\ba-\b-f\bfl\bla\bag\bg is a
- synonym for this variable.
- i\bis\bse\bea\bar\brc\bch\bh-\b-t\bte\ber\brm\bmi\bin\bna\bat\bto\bor\brs\bs (\b(`\b``\b`C\bC-\b-[\b[C\bC-\b-J\bJ'\b''\b')\b)
- The string of characters that should terminate an
- incremental search without subsequently executing
- the character as a command. If this variable has
- not been given a value, the characters _\bE_\bS_\bC and _\bC_\b-_\bJ
- will terminate an incremental search.
- k\bke\bey\bym\bma\bap\bp (\b(e\bem\bma\bac\bcs\bs)\b)
- Set the current readline keymap. The set of legal
- keymap names is _\be_\bm_\ba_\bc_\bs_\b, _\be_\bm_\ba_\bc_\bs_\b-_\bs_\bt_\ba_\bn_\bd_\ba_\br_\bd_\b, _\be_\bm_\ba_\bc_\bs_\b-_\bm_\be_\bt_\ba_\b,
- _\be_\bm_\ba_\bc_\bs_\b-_\bc_\bt_\bl_\bx_\b, _\bv_\bi_\b, _\bv_\bi_\b-_\bm_\bo_\bv_\be_\b, _\bv_\bi_\b-_\bc_\bo_\bm_\bm_\ba_\bn_\bd, and _\bv_\bi_\b-_\bi_\bn_\bs_\be_\br_\bt.
- _\bv_\bi is equivalent to _\bv_\bi_\b-_\bc_\bo_\bm_\bm_\ba_\bn_\bd; _\be_\bm_\ba_\bc_\bs is equivalent
- to _\be_\bm_\ba_\bc_\bs_\b-_\bs_\bt_\ba_\bn_\bd_\ba_\br_\bd. The default value is _\be_\bm_\ba_\bc_\bs; the
- value of e\bed\bdi\bit\bti\bin\bng\bg-\b-m\bmo\bod\bde\be also affects the default
- keymap.
- m\bma\bar\brk\bk-\b-d\bdi\bir\bre\bec\bct\bto\bor\bri\bie\bes\bs (\b(O\bOn\bn)\b)
- If set to O\bOn\bn, complete<d directory names have a
- slash appended.
- m\bma\bar\brk\bk-\b-m\bmo\bod\bdi\bif\bfi\bie\bed\bd-\b-l\bli\bin\bne\bes\bs (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, history lines that have been modified
- are displayed with a preceding asterisk (*\b*).
- o\bou\but\btp\bpu\but\bt-\b-m\bme\bet\bta\ba (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, readline will display characters with
- the eighth bit set directly rather than as a meta-
- prefixed escape sequence.
- p\bpr\bri\bin\bnt\bt-\b-c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bns\bs-\b-h\bho\bor\bri\biz\bzo\bon\bnt\bta\bal\bll\bly\by (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, readline will display completions
- with matches sorted horizontally in alphabetical
- order, rather than down the screen.
- s\bsh\bho\bow\bw-\b-a\bal\bll\bl-\b-i\bif\bf-\b-a\bam\bmb\bbi\big\bgu\buo\bou\bus\bs (\b(O\bOf\bff\bf)\b)
- This alters the default behavior of the completion
- functions. If set to o\bon\bn, words which have more
- than one possible completion cause the matches to
- be listed immediately instead of ringing the bell.
- v\bvi\bis\bsi\bib\bbl\ble\be-\b-s\bst\bta\bat\bts\bs (\b(O\bOf\bff\bf)\b)
- If set to O\bOn\bn, a character denoting a file's type as
- reported by s\bst\bta\bat\bt(2) is appended to the filename
- when listing possible completions.
-
- C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl C\bCo\bon\bns\bst\btr\bru\buc\bct\bts\bs
- Readline implements a facility similar in spirit to the
- conditional compilation features of the C preprocessor
- which allows key bindings and variable settings to be
-
-
-
- GNU 1998 Dec 31 5
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- performed as the result of tests. There are four parser
- directives used.
-
- $\b$i\bif\bf The $\b$i\bif\bf construct allows bindings to be made based
- on the editing mode, the terminal being used, or
- the application using readline. The text of the
- test extends to the end of the line; no characters
- are required to isolate it.
-
- m\bmo\bod\bde\be The m\bmo\bod\bde\be=\b= form of the $\b$i\bif\bf directive is used
- to test whether readline is in emacs or vi
- mode. This may be used in conjunction with
- the s\bse\bet\bt k\bke\bey\bym\bma\bap\bp command, for instance, to set
- bindings in the _\be_\bm_\ba_\bc_\bs_\b-_\bs_\bt_\ba_\bn_\bd_\ba_\br_\bd and _\be_\bm_\ba_\bc_\bs_\b-
- _\bc_\bt_\bl_\bx keymaps only if readline is starting
- out in emacs mode.
-
- t\bte\ber\brm\bm The t\bte\ber\brm\bm=\b= form may be used to include termi-
- nal-specific key bindings, perhaps to bind
- the key sequences output by the terminal's
- function keys. The word on the right side
- of the =\b= is tested against the full name of
- the terminal and the portion of the terminal
- name before the first -\b-. This allows _\bs_\bu_\bn to
- match both _\bs_\bu_\bn and _\bs_\bu_\bn_\b-_\bc_\bm_\bd, for instance.
-
- a\bap\bpp\bpl\bli\bic\bca\bat\bti\bio\bon\bn
- The a\bap\bpp\bpl\bli\bic\bca\bat\bti\bio\bon\bn construct is used to include
- application-specific settings. Each program
- using the readline library sets the _\ba_\bp_\bp_\bl_\bi_\bc_\ba_\b-
- _\bt_\bi_\bo_\bn _\bn_\ba_\bm_\be, and an initialization file can
- test for a particular value. This could be
- used to bind key sequences to functions use-
- ful for a specific program. For instance,
- the following command adds a key sequence
- that quotes the current or previous word in
- Bash:
-
- $\b$i\bif\bf bash
- # Quote the current or previous word
- "\C-xq": "\eb\"\ef\""
- $\b$e\ben\bnd\bdi\bif\bf
-
- $\b$e\ben\bnd\bdi\bif\bf This command, as seen in the previous example, ter-
- minates an $\b$i\bif\bf command.
-
- $\b$e\bel\bls\bse\be Commands in this branch of the $\b$i\bif\bf directive are
- executed if the test fails.
-
- $\b$i\bin\bnc\bcl\blu\bud\bde\be
- This directive takes a single filename as an argu-
- ment and reads commands and bindings from that
- file. For example, the following directive would
- read _\b/_\be_\bt_\bc_\b/_\bi_\bn_\bp_\bu_\bt_\br_\bc:
-
-
-
- GNU 1998 Dec 31 6
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- $\b$i\bin\bnc\bcl\blu\bud\bde\be _\b/_\be_\bt_\bc_\b/_\bi_\bn_\bp_\bu_\bt_\br_\bc
-
- S\bSE\bEA\bAR\bRC\bCH\bHI\bIN\bNG\bG
- Readline provides commands for searching through the com-
- mand history for lines containing a specified string.
- There are two search modes: _\bi_\bn_\bc_\br_\be_\bm_\be_\bn_\bt_\ba_\bl and _\bn_\bo_\bn_\b-_\bi_\bn_\bc_\br_\be_\bm_\be_\bn_\b-
- _\bt_\ba_\bl.
-
- Incremental searches begin before the user has finished
- typing the search string. As each character of the search
- string is typed, readline displays the next entry from the
- history matching the string typed so far. An incremental
- search requires only as many characters as needed to find
- the desired history entry. The characters present in the
- value of the _\bi_\bs_\be_\ba_\br_\bc_\bh_\b-_\bt_\be_\br_\bm_\bi_\bn_\ba_\bt_\bo_\br_\bs variable are used to ter-
- minate an incremental search. If that variable has not
- been assigned a value the Escape and Control-J characters
- will terminate an incremental search. Control-G will
- abort an incremental search and restore the original line.
- When the search is terminated, the history entry contain-
- ing the search string becomes the current line. To find
- other matching entries in the history list, type Control-S
- or Control-R as appropriate. This will search backward or
- forward in the history for the next line matching the
- search string typed so far. Any other key sequence bound
- to a readline command will terminate the search and exe-
- cute that command. For instance, a _\bn_\be_\bw_\bl_\bi_\bn_\be will terminate
- the search and accept the line, thereby executing the com-
- mand from the history list.
-
- Non-incremental searches read the entire search string
- before starting to search for matching history lines. The
- search string may be typed by the user or be part of the
- contents of the current line.
-
- E\bED\bDI\bIT\bTI\bIN\bNG\bG C\bCO\bOM\bMM\bMA\bAN\bND\bDS\bS
- The following is a list of the names of the commands and
- the default key sequences to which they are bound. Com-
- mand names without an accompanying key sequence are
- unbound by default.
-
- C\bCo\bom\bmm\bma\ban\bnd\bds\bs f\bfo\bor\br M\bMo\bov\bvi\bin\bng\bg
- b\bbe\beg\bgi\bin\bnn\bni\bin\bng\bg-\b-o\bof\bf-\b-l\bli\bin\bne\be (\b(C\bC-\b-a\ba)\b)
- Move to the start of the current line.
- e\ben\bnd\bd-\b-o\bof\bf-\b-l\bli\bin\bne\be (\b(C\bC-\b-e\be)\b)
- Move to the end of the line.
- f\bfo\bor\brw\bwa\bar\brd\bd-\b-c\bch\bha\bar\br (\b(C\bC-\b-f\bf)\b)
- Move forward a character.
- b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-c\bch\bha\bar\br (\b(C\bC-\b-b\bb)\b)
- Move back a character.
- f\bfo\bor\brw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-f\bf)\b)
- Move forward to the end of the next word. Words
- are composed of alphanumeric characters (letters
- and digits).
-
-
-
- GNU 1998 Dec 31 7
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-b\bb)\b)
- Move back to the start of this, or the previous,
- word. Words are composed of alphanumeric charac-
- ters (letters and digits).
- c\bcl\ble\bea\bar\br-\b-s\bsc\bcr\bre\bee\ben\bn (\b(C\bC-\b-l\bl)\b)
- Clear the screen leaving the current line at the
- top of the screen. With an argument, refresh the
- current line without clearing the screen.
- r\bre\bed\bdr\bra\baw\bw-\b-c\bcu\bur\brr\bre\ben\bnt\bt-\b-l\bli\bin\bne\be
- Refresh the current line.
-
- C\bCo\bom\bmm\bma\ban\bnd\bds\bs f\bfo\bor\br M\bMa\ban\bni\bip\bpu\bul\bla\bat\bti\bin\bng\bg t\bth\bhe\be H\bHi\bis\bst\bto\bor\bry\by
- a\bac\bcc\bce\bep\bpt\bt-\b-l\bli\bin\bne\be (\b(N\bNe\bew\bwl\bli\bin\bne\be,\b, R\bRe\bet\btu\bur\brn\bn)\b)
- Accept the line regardless of where the cursor is.
- If this line is non-empty, add it to the history
- list. If the line is a modified history line, then
- restore the history line to its original state.
- p\bpr\bre\bev\bvi\bio\bou\bus\bs-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(C\bC-\b-p\bp)\b)
- Fetch the previous command from the history list,
- moving back in the list.
- n\bne\bex\bxt\bt-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(C\bC-\b-n\bn)\b)
- Fetch the next command from the history list, mov-
- ing forward in the list.
- b\bbe\beg\bgi\bin\bnn\bni\bin\bng\bg-\b-o\bof\bf-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(M\bM-\b-<\b<)\b)
- Move to the first line in the history.
- e\ben\bnd\bd-\b-o\bof\bf-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(M\bM-\b->\b>)\b)
- Move to the end of the input history, i.e., the
- line currently being entered.
- r\bre\bev\bve\ber\brs\bse\be-\b-s\bse\bea\bar\brc\bch\bh-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(C\bC-\b-r\br)\b)
- Search backward starting at the current line and
- moving `up' through the history as necessary. This
- is an incremental search.
- f\bfo\bor\brw\bwa\bar\brd\bd-\b-s\bse\bea\bar\brc\bch\bh-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(C\bC-\b-s\bs)\b)
- Search forward starting at the current line and
- moving `down' through the history as necessary.
- This is an incremental search.
- n\bno\bon\bn-\b-i\bin\bnc\bcr\bre\bem\bme\ben\bnt\bta\bal\bl-\b-r\bre\bev\bve\ber\brs\bse\be-\b-s\bse\bea\bar\brc\bch\bh-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(M\bM-\b-p\bp)\b)
- Search backward through the history starting at the
- current line using a non-incremental search for a
- string supplied by the user.
- n\bno\bon\bn-\b-i\bin\bnc\bcr\bre\bem\bme\ben\bnt\bta\bal\bl-\b-f\bfo\bor\brw\bwa\bar\brd\bd-\b-s\bse\bea\bar\brc\bch\bh-\b-h\bhi\bis\bst\bto\bor\bry\by (\b(M\bM-\b-n\bn)\b)
- Search forward through the history using a non-
- incremental search for a string supplied by the
- user.
- h\bhi\bis\bst\bto\bor\bry\by-\b-s\bse\bea\bar\brc\bch\bh-\b-f\bfo\bor\brw\bwa\bar\brd\bd
- Search forward through the history for the string
- of characters between the start of the current line
- and the current cursor position (the _\bp_\bo_\bi_\bn_\bt). This
- is a non-incremental search.
- h\bhi\bis\bst\bto\bor\bry\by-\b-s\bse\bea\bar\brc\bch\bh-\b-b\bba\bac\bck\bkw\bwa\bar\brd\bd
- Search backward through the history for the string
- of characters between the start of the current line
- and the point. This is a non-incremental search.
-
-
-
-
- GNU 1998 Dec 31 8
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- y\bya\ban\bnk\bk-\b-n\bnt\bth\bh-\b-a\bar\brg\bg (\b(M\bM-\b-C\bC-\b-y\by)\b)
- Insert the first argument to the previous command
- (usually the second word on the previous line) at
- point (the current cursor position). With an argu-
- ment _\bn, insert the _\bnth word from the previous com-
- mand (the words in the previous command begin with
- word 0). A negative argument inserts the _\bnth word
- from the end of the previous command.
- y\bya\ban\bnk\bk-\b-l\bla\bas\bst\bt-\b-a\bar\brg\bg (\b(M\bM-\b-.\b.,\b, M\bM-\b-_\b_)\b)
- Insert the last argument to the previous command
- (the last word of the previous history entry).
- With an argument, behave exactly like y\bya\ban\bnk\bk-\b-n\bnt\bth\bh-\b-a\bar\brg\bg.
- Successive calls to y\bya\ban\bnk\bk-\b-l\bla\bas\bst\bt-\b-a\bar\brg\bg move back through
- the history list, inserting the last argument of
- each line in turn.
-
- C\bCo\bom\bmm\bma\ban\bnd\bds\bs f\bfo\bor\br C\bCh\bha\ban\bng\bgi\bin\bng\bg T\bTe\bex\bxt\bt
- d\bde\bel\ble\bet\bte\be-\b-c\bch\bha\bar\br (\b(C\bC-\b-d\bd)\b)
- Delete the character under the cursor. If point is
- at the beginning of the line, there are no charac-
- ters in the line, and the last character typed was
- not bound to B\bBd\bde\bel\ble\bet\bte\be-\b-c\bch\bha\bar\br, then return E\bEO\bOF\bF.
- b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-d\bde\bel\ble\bet\bte\be-\b-c\bch\bha\bar\br (\b(R\bRu\bub\bbo\bou\but\bt)\b)
- Delete the character behind the cursor. When given
- a numeric argument, save the deleted text on the
- kill ring.
- f\bfo\bor\brw\bwa\bar\brd\bd-\b-b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-d\bde\bel\ble\bet\bte\be-\b-c\bch\bha\bar\br
- Delete the character under the cursor, unless the
- cursor is at the end of the line, in which case the
- character behind the cursor is deleted. By
- default, this is not bound to a key.
- q\bqu\buo\bot\bte\bed\bd-\b-i\bin\bns\bse\ber\brt\bt (\b(C\bC-\b-q\bq,\b, C\bC-\b-v\bv)\b)
- Add the next character that you type to the line
- verbatim. This is how to insert characters like
- C\bC-\b-q\bq, for example.
- t\bta\bab\bb-\b-i\bin\bns\bse\ber\brt\bt (\b(M\bM-\b-T\bTA\bAB\bB)\b)
- Insert a tab character.
- s\bse\bel\blf\bf-\b-i\bin\bns\bse\ber\brt\bt (\b(a\ba,\b, b\bb,\b, A\bA,\b, 1\b1,\b, !\b!,\b, .\b..\b..\b.)\b)
- Insert the character typed.
- t\btr\bra\ban\bns\bsp\bpo\bos\bse\be-\b-c\bch\bha\bar\brs\bs (\b(C\bC-\b-t\bt)\b)
- Drag the character before point forward over the
- character at point. Point moves forward as well.
- If point is at the end of the line, then transpose
- the two characters before point. Negative argu-
- ments don't work.
- t\btr\bra\ban\bns\bsp\bpo\bos\bse\be-\b-w\bwo\bor\brd\bds\bs (\b(M\bM-\b-t\bt)\b)
- Drag the word behind the cursor past the word in
- front of the cursor moving the cursor over that
- word as well.
- u\bup\bpc\bca\bas\bse\be-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-u\bu)\b)
- Uppercase the current (or following) word. With a
- negative argument, uppercase the previous word, but
- do not move point.
-
-
-
-
- GNU 1998 Dec 31 9
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- d\bdo\bow\bwn\bnc\bca\bas\bse\be-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-l\bl)\b)
- Lowercase the current (or following) word. With a
- negative argument, lowercase the previous word, but
- do not move point.
- c\bca\bap\bpi\bit\bta\bal\bli\biz\bze\be-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-c\bc)\b)
- Capitalize the current (or following) word. With a
- negative argument, capitalize the previous word,
- but do not move point.
-
- K\bKi\bil\bll\bli\bin\bng\bg a\ban\bnd\bd Y\bYa\ban\bnk\bki\bin\bng\bg
- k\bki\bil\bll\bl-\b-l\bli\bin\bne\be (\b(C\bC-\b-k\bk)\b)
- Kill the text from the current cursor position to
- the end of the line.
- b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-k\bki\bil\bll\bl-\b-l\bli\bin\bne\be (\b(C\bC-\b-x\bx R\bRu\bub\bbo\bou\but\bt)\b)
- Kill backward to the beginning of the line.
- u\bun\bni\bix\bx-\b-l\bli\bin\bne\be-\b-d\bdi\bis\bsc\bca\bar\brd\bd (\b(C\bC-\b-u\bu)\b)
- Kill backward from point to the beginning of the
- line. The killed text is saved on the kill-ring.
- k\bki\bil\bll\bl-\b-w\bwh\bho\bol\ble\be-\b-l\bli\bin\bne\be
- Kill all characters on the current line, no matter
- where the cursor is.
- k\bki\bil\bll\bl-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-d\bd)\b)
- Kill from the cursor to the end of the current
- word, or if between words, to the end of the next
- word. Word boundaries are the same as those used
- by f\bfo\bor\brw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd.
- b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-k\bki\bil\bll\bl-\b-w\bwo\bor\brd\bd (\b(M\bM-\b-R\bRu\bub\bbo\bou\but\bt)\b)
- Kill the word behind the cursor. Word boundaries
- are the same as those used by b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd.
- u\bun\bni\bix\bx-\b-w\bwo\bor\brd\bd-\b-r\bru\bub\bbo\bou\but\bt (\b(C\bC-\b-w\bw)\b)
- Kill the word behind the cursor, using white space
- as a word boundary. The word boundaries are dif-
- ferent from b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-k\bki\bil\bll\bl-\b-w\bwo\bor\brd\bd.
- d\bde\bel\ble\bet\bte\be-\b-h\bho\bor\bri\biz\bzo\bon\bnt\bta\bal\bl-\b-s\bsp\bpa\bac\bce\be (\b(M\bM-\b-\\b\)\b)
- Delete all spaces and tabs around point.
- k\bki\bil\bll\bl-\b-r\bre\beg\bgi\bio\bon\bn
- Kill the text between the point and _\bm_\ba_\br_\bk (saved
- cursor position). This text is referred to as the
- _\br_\be_\bg_\bi_\bo_\bn.
- c\bco\bop\bpy\by-\b-r\bre\beg\bgi\bio\bon\bn-\b-a\bas\bs-\b-k\bki\bil\bll\bl
- Copy the text in the region to the kill buffer.
- c\bco\bop\bpy\by-\b-b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd
- Copy the word before point to the kill buffer. The
- word boundaries are the same as b\bba\bac\bck\bkw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd.
- c\bco\bop\bpy\by-\b-f\bfo\bor\brw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd
- Copy the word following point to the kill buffer.
- The word boundaries are the same as f\bfo\bor\brw\bwa\bar\brd\bd-\b-w\bwo\bor\brd\bd.
- y\bya\ban\bnk\bk (\b(C\bC-\b-y\by)\b)
- Yank the top of the kill ring into the buffer at
- the cursor.
- y\bya\ban\bnk\bk-\b-p\bpo\bop\bp (\b(M\bM-\b-y\by)\b)
- Rotate the kill ring, and yank the new top. Only
- works following y\bya\ban\bnk\bk or y\bya\ban\bnk\bk-\b-p\bpo\bop\bp.
-
-
-
-
- GNU 1998 Dec 31 10
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- N\bNu\bum\bme\ber\bri\bic\bc A\bAr\brg\bgu\bum\bme\ben\bnt\bts\bs
- d\bdi\big\bgi\bit\bt-\b-a\bar\brg\bgu\bum\bme\ben\bnt\bt (\b(M\bM-\b-0\b0,\b, M\bM-\b-1\b1,\b, .\b..\b..\b.,\b, M\bM-\b--\b-)\b)
- Add this digit to the argument already accumulat-
- ing, or start a new argument. M-- starts a nega-
- tive argument.
- u\bun\bni\biv\bve\ber\brs\bsa\bal\bl-\b-a\bar\brg\bgu\bum\bme\ben\bnt\bt
- This is another way to specify an argument. If
- this command is followed by one or more digits,
- optionally with a leading minus sign, those digits
- define the argument. If the command is followed by
- digits, executing u\bun\bni\biv\bve\ber\brs\bsa\bal\bl-\b-a\bar\brg\bgu\bum\bme\ben\bnt\bt again ends the
- numeric argument, but is otherwise ignored. As a
- special case, if this command is immediately fol-
- lowed by a character that is neither a digit or
- minus sign, the argument count for the next command
- is multiplied by four. The argument count is ini-
- tially one, so executing this function the first
- time makes the argument count four, a second time
- makes the argument count sixteen, and so on.
-
- C\bCo\bom\bmp\bpl\ble\bet\bti\bin\bng\bg
- c\bco\bom\bmp\bpl\ble\bet\bte\be (\b(T\bTA\bAB\bB)\b)
- Attempt to perform completion on the text before
- point. The actual completion performed is applica-
- tion-specific. B\bBa\bas\bsh\bh, for instance, attempts com-
- pletion treating the text as a variable (if the
- text begins with $\b$), username (if the text begins
- with ~\b~), hostname (if the text begins with @\b@), or
- command (including aliases and functions) in turn.
- If none of these produces a match, filename comple-
- tion is attempted. G\bGd\bdb\bb, on the other hand, allows
- completion of program functions and variables, and
- only attempts filename completion under certain
- circumstances.
- p\bpo\bos\bss\bsi\bib\bbl\ble\be-\b-c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bns\bs (\b(M\bM-\b-?\b?)\b)
- List the possible completions of the text before
- point.
- i\bin\bns\bse\ber\brt\bt-\b-c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bns\bs (\b(M\bM-\b-*\b*)\b)
- Insert all completions of the text before point
- that would have been generated by p\bpo\bos\bss\bsi\bib\bbl\ble\be-\b-c\bco\bom\bmp\bpl\ble\be-\b-
- t\bti\bio\bon\bns\bs.
- m\bme\ben\bnu\bu-\b-c\bco\bom\bmp\bpl\ble\bet\bte\be
- Similar to c\bco\bom\bmp\bpl\ble\bet\bte\be, but replaces the word to be
- completed with a single match from the list of pos-
- sible completions. Repeated execution of m\bme\ben\bnu\bu-\b-c\bco\bom\bm-\b-
- p\bpl\ble\bet\bte\be steps through the list of possible comple-
- tions, inserting each match in turn. At the end of
- the list of completions, the bell is rung and the
- original text is restored. An argument of _\bn moves
- _\bn positions forward in the list of matches; a nega-
- tive argument may be used to move backward through
- the list. This command is intended to be bound to
- T\bTA\bAB\bB, but is unbound by default.
-
-
-
-
- GNU 1998 Dec 31 11
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- d\bde\bel\ble\bet\bte\be-\b-c\bch\bha\bar\br-\b-o\bor\br-\b-l\bli\bis\bst\bt
- Deletes the character under the cursor if not at
- the beginning or end of the line (like d\bde\bel\ble\bet\bte\be-\b-
- c\bch\bha\bar\br). If at the end of the line, behaves identi-
- cally to p\bpo\bos\bss\bsi\bib\bbl\ble\be-\b-c\bco\bom\bmp\bpl\ble\bet\bti\bio\bon\bns\bs. This command is
- unbound by default.
-
- K\bKe\bey\byb\bbo\boa\bar\brd\bd M\bMa\bac\bcr\bro\bos\bs
- s\bst\bta\bar\brt\bt-\b-k\bkb\bbd\bd-\b-m\bma\bac\bcr\bro\bo (\b(C\bC-\b-x\bx (\b()\b)
- Begin saving the characters typed into the current
- keyboard macro.
- e\ben\bnd\bd-\b-k\bkb\bbd\bd-\b-m\bma\bac\bcr\bro\bo (\b(C\bC-\b-x\bx )\b))\b)
- Stop saving the characters typed into the current
- keyboard macro and store the definition.
- c\bca\bal\bll\bl-\b-l\bla\bas\bst\bt-\b-k\bkb\bbd\bd-\b-m\bma\bac\bcr\bro\bo (\b(C\bC-\b-x\bx e\be)\b)
- Re-execute the last keyboard macro defined, by mak-
- ing the characters in the macro appear as if typed
- at the keyboard.
-
- M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs
- r\bre\be-\b-r\bre\bea\bad\bd-\b-i\bin\bni\bit\bt-\b-f\bfi\bil\ble\be (\b(C\bC-\b-x\bx C\bC-\b-r\br)\b)
- Read in the contents of the _\bi_\bn_\bp_\bu_\bt_\br_\bc file, and
- incorporate any bindings or variable assignments
- found there.
- a\bab\bbo\bor\brt\bt (\b(C\bC-\b-g\bg)\b)
- Abort the current editing command and ring the ter-
- minal's bell (subject to the setting of
- b\bbe\bel\bll\bl-\b-s\bst\bty\byl\ble\be).
- d\bdo\bo-\b-u\bup\bpp\bpe\ber\brc\bca\bas\bse\be-\b-v\bve\ber\brs\bsi\bio\bon\bn (\b(M\bM-\b-a\ba,\b, M\bM-\b-b\bb,\b, M\bM-\b-_\bx,\b, .\b..\b..\b.)\b)
- If the metafied character _\bx is lowercase, run the
- command that is bound to the corresponding upper-
- case character.
- p\bpr\bre\bef\bfi\bix\bx-\b-m\bme\bet\bta\ba (\b(E\bES\bSC\bC)\b)
- Metafy the next character typed. E\bES\bSC\bC f\bf is equiva-
- lent to M\bMe\bet\bta\ba-\b-f\bf.
- u\bun\bnd\bdo\bo (\b(C\bC-\b-_\b_,\b, C\bC-\b-x\bx C\bC-\b-u\bu)\b)
- Incremental undo, separately remembered for each
- line.
- r\bre\bev\bve\ber\brt\bt-\b-l\bli\bin\bne\be (\b(M\bM-\b-r\br)\b)
- Undo all changes made to this line. This is like
- executing the u\bun\bnd\bdo\bo command enough times to return
- the line to its initial state.
- t\bti\bil\bld\bde\be-\b-e\bex\bxp\bpa\ban\bnd\bd (\b(M\bM-\b-&\b&)\b)
- Perform tilde expansion on the current word.
- s\bse\bet\bt-\b-m\bma\bar\brk\bk (\b(C\bC-\b-@\b@,\b, M\bM-\b-<\b<s\bsp\bpa\bac\bce\be>\b>)\b)
- Set the mark to the current point. If a numeric
- argument is supplied, the mark is set to that posi-
- tion.
- e\bex\bxc\bch\bha\ban\bng\bge\be-\b-p\bpo\boi\bin\bnt\bt-\b-a\ban\bnd\bd-\b-m\bma\bar\brk\bk (\b(C\bC-\b-x\bx C\bC-\b-x\bx)\b)
- Swap the point with the mark. The current cursor
- position is set to the saved position, and the old
- cursor position is saved as the mark.
- c\bch\bha\bar\bra\bac\bct\bte\ber\br-\b-s\bse\bea\bar\brc\bch\bh (\b(C\bC-\b-]\b])\b)
- A character is read and point is moved to the next
-
-
-
- GNU 1998 Dec 31 12
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- occurrence of that character. A negative count
- searches for previous occurrences.
- c\bch\bha\bar\bra\bac\bct\bte\ber\br-\b-s\bse\bea\bar\brc\bch\bh-\b-b\bba\bac\bck\bkw\bwa\bar\brd\bd (\b(M\bM-\b-C\bC-\b-]\b])\b)
- A character is read and point is moved to the pre-
- vious occurrence of that character. A negative
- count searches for subsequent occurrences.
- i\bin\bns\bse\ber\brt\bt-\b-c\bco\bom\bmm\bme\ben\bnt\bt (\b(M\bM-\b-#\b#)\b)
- The value of the readline c\bco\bom\bmm\bme\ben\bnt\bt-\b-b\bbe\beg\bgi\bin\bn variable is
- inserted at the beginning of the current line, and
- the line is accepted as if a newline had been
- typed. This makes the current line a shell com-
- ment.
- d\bdu\bum\bmp\bp-\b-f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs
- Print all of the functions and their key bindings
- to the readline output stream. If a numeric argu-
- ment is supplied, the output is formatted in such a
- way that it can be made part of an _\bi_\bn_\bp_\bu_\bt_\br_\bc file.
- d\bdu\bum\bmp\bp-\b-v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
- Print all of the settable variables and their val-
- ues to the readline output stream. If a numeric
- argument is supplied, the output is formatted in
- such a way that it can be made part of an _\bi_\bn_\bp_\bu_\bt_\br_\bc
- file.
- d\bdu\bum\bmp\bp-\b-m\bma\bac\bcr\bro\bos\bs
- Print all of the readline key sequences bound to
- macros and the strings they ouput. If a numeric
- argument is supplied, the output is formatted in
- such a way that it can be made part of an _\bi_\bn_\bp_\bu_\bt_\br_\bc
- file.
- e\bem\bma\bac\bcs\bs-\b-e\bed\bdi\bit\bti\bin\bng\bg-\b-m\bmo\bod\bde\be (\b(C\bC-\b-e\be)\b)
- When in v\bvi\bi editing mode, this causes a switch to
- e\bem\bma\bac\bcs\bs editing mode.
- v\bvi\bi-\b-e\bed\bdi\bit\bti\bin\bng\bg-\b-m\bmo\bod\bde\be (\b(M\bM-\b-C\bC-\b-j\bj)\b)
- When in e\bem\bma\bac\bcs\bs editing mode, this causes a switch to
- v\bvi\bi editing mode.
-
- D\bDE\bEF\bFA\bAU\bUL\bLT\bT K\bKE\bEY\bY B\bBI\bIN\bND\bDI\bIN\bNG\bGS\bS
- The following is a list of the default emacs and vi bind-
- ings. Characters with the 8th bit set are written as
- M-<character>, and are referred to as _\bm_\be_\bt_\ba_\bf_\bi_\be_\bd characters.
- The printable ASCII characters not mentioned in the list
- of emacs standard bindings are bound to the _\bs_\be_\bl_\bf_\b-_\bi_\bn_\bs_\be_\br_\bt
- function, which just inserts the given character into the
- input line. In vi insertion mode, all characters not
- specifically mentioned are bound to _\bs_\be_\bl_\bf_\b-_\bi_\bn_\bs_\be_\br_\bt. Charac-
- ters assigned to signal generation by _\bs_\bt_\bt_\by(1) or the ter-
- minal driver, such as C-Z or C-C, retain that function.
- Upper and lower case _\bm_\be_\bt_\ba_\bf_\bi_\be_\bd characters are bound to the
- same function in the emacs mode meta keymap. The remain-
- ing characters are unbound, which causes readline to ring
- the bell (subject to the setting of the b\bbe\bel\bll\bl-\b-s\bst\bty\byl\ble\be vari-
- able).
-
-
-
-
-
- GNU 1998 Dec 31 13
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- E\bEm\bma\bac\bcs\bs M\bMo\bod\bde\be
- Emacs Standard bindings
-
- "C-@" set-mark
- "C-A" beginning-of-line
- "C-B" backward-char
- "C-D" delete-char
- "C-E" end-of-line
- "C-F" forward-char
- "C-G" abort
- "C-H" backward-delete-char
- "C-I" complete
- "C-J" accept-line
- "C-K" kill-line
- "C-L" clear-screen
- "C-M" accept-line
- "C-N" next-history
- "C-P" previous-history
- "C-Q" quoted-insert
- "C-R" reverse-search-history
- "C-S" forward-search-history
- "C-T" transpose-chars
- "C-U" unix-line-discard
- "C-V" quoted-insert
- "C-W" unix-word-rubout
- "C-Y" yank
- "C-]" character-search
- "C-_" undo
- " " to "/" self-insert
- "0" to "9" self-insert
- ":" to "~" self-insert
- "C-?" backward-delete-char
-
- Emacs Meta bindings
-
- "M-C-G" abort
- "M-C-H" backward-kill-word
- "M-C-I" tab-insert
- "M-C-J" vi-editing-mode
- "M-C-M" vi-editing-mode
- "M-C-R" revert-line
- "M-C-Y" yank-nth-arg
- "M-C-[" complete
- "M-C-]" character-search-backward
- "M-space" set-mark
- "M-#" insert-comment
- "M-&" tilde-expand
- "M-*" insert-completions
- "M--" digit-argument
- "M-." yank-last-arg
- "M-0" digit-argument
- "M-1" digit-argument
- "M-2" digit-argument
- "M-3" digit-argument
-
-
-
- GNU 1998 Dec 31 14
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- "M-4" digit-argument
- "M-5" digit-argument
- "M-6" digit-argument
- "M-7" digit-argument
- "M-8" digit-argument
- "M-9" digit-argument
- "M-<" beginning-of-history
- "M-=" possible-completions
- "M->" end-of-history
- "M-?" possible-completions
- "M-B" backward-word
- "M-C" capitalize-word
- "M-D" kill-word
- "M-F" forward-word
- "M-L" downcase-word
- "M-N" non-incremental-forward-search-history
- "M-P" non-incremental-reverse-search-history
- "M-R" revert-line
- "M-T" transpose-words
- "M-U" upcase-word
- "M-Y" yank-pop
- "M-\" delete-horizontal-space
- "M-~" tilde-expand
- "M-C-?" backward-delete-word
- "M-_" yank-last-arg
-
- Emacs Control-X bindings
-
- "C-XC-G" abort
- "C-XC-R" re-read-init-file
- "C-XC-U" undo
- "C-XC-X" exchange-point-and-mark
- "C-X(" start-kbd-macro
- "C-X)" end-kbd-macro
- "C-XE" call-last-kbd-macro
- "C-XC-?" backward-kill-line
-
-
- V\bVI\bI M\bMo\bod\bde\be b\bbi\bin\bnd\bdi\bin\bng\bgs\bs
- VI Insert Mode functions
-
- "C-D" vi-eof-maybe
- "C-H" backward-delete-char
- "C-I" complete
- "C-J" accept-line
- "C-M" accept-line
- "C-R" reverse-search-history
- "C-S" forward-search-history
- "C-T" transpose-chars
- "C-U" unix-line-discard
- "C-V" quoted-insert
- "C-W" unix-word-rubout
- "C-Y" yank
- "C-[" vi-movement-mode
-
-
-
- GNU 1998 Dec 31 15
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- "C-_" undo
- " " to "~" self-insert
- "C-?" backward-delete-char
-
- VI Command Mode functions
-
- "C-D" vi-eof-maybe
- "C-E" emacs-editing-mode
- "C-G" abort
- "C-H" backward-char
- "C-J" accept-line
- "C-K" kill-line
- "C-L" clear-screen
- "C-M" accept-line
- "C-N" next-history
- "C-P" previous-history
- "C-Q" quoted-insert
- "C-R" reverse-search-history
- "C-S" forward-search-history
- "C-T" transpose-chars
- "C-U" unix-line-discard
- "C-V" quoted-insert
- "C-W" unix-word-rubout
- "C-Y" yank
- " " forward-char
- "#" insert-comment
- "$" end-of-line
- "%" vi-match
- "&" vi-tilde-expand
- "*" vi-complete
- "+" next-history
- "," vi-char-search
- "-" previous-history
- "." vi-redo
- "/" vi-search
- "0" beginning-of-line
- "1" to "9" vi-arg-digit
- ";" vi-char-search
- "=" vi-complete
- "?" vi-search
- "A" vi-append-eol
- "B" vi-prev-word
- "C" vi-change-to
- "D" vi-delete-to
- "E" vi-end-word
- "F" vi-char-search
- "G" vi-fetch-history
- "I" vi-insert-beg
- "N" vi-search-again
- "P" vi-put
- "R" vi-replace
- "S" vi-subst
- "T" vi-char-search
- "U" revert-line
-
-
-
- GNU 1998 Dec 31 16
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- "W" vi-next-word
- "X" backward-delete-char
- "Y" vi-yank-to
- "\" vi-complete
- "^" vi-first-print
- "_" vi-yank-arg
- "`" vi-goto-mark
- "a" vi-append-mode
- "b" vi-prev-word
- "c" vi-change-to
- "d" vi-delete-to
- "e" vi-end-word
- "f" vi-char-search
- "h" backward-char
- "i" vi-insertion-mode
- "j" next-history
- "k" prev-history
- "l" forward-char
- "m" vi-set-mark
- "n" vi-search-again
- "p" vi-put
- "r" vi-change-char
- "s" vi-subst
- "t" vi-char-search
- "u" undo
- "w" vi-next-word
- "x" vi-delete
- "y" vi-yank-to
- "|" vi-column
- "~" vi-change-case
-
- S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- _\bT_\bh_\be _\bG_\bn_\bu _\bR_\be_\ba_\bd_\bl_\bi_\bn_\be _\bL_\bi_\bb_\br_\ba_\br_\by, Brian Fox and Chet Ramey
- _\bT_\bh_\be _\bG_\bn_\bu _\bH_\bi_\bs_\bt_\bo_\br_\by _\bL_\bi_\bb_\br_\ba_\br_\by, Brian Fox and Chet Ramey
- _\bb_\ba_\bs_\bh(1)
-
- F\bFI\bIL\bLE\bES\bS
- _\b~_\b/_\b._\bi_\bn_\bp_\bu_\bt_\br_\bc
- Individual r\bre\bea\bad\bdl\bli\bin\bne\be initialization file
-
- A\bAU\bUT\bTH\bHO\bOR\bRS\bS
- Brian Fox, Free Software Foundation (primary author)
- bfox@ai.MIT.Edu
-
- Chet Ramey, Case Western Reserve University
- chet@ins.CWRU.Edu
-
- B\bBU\bUG\bG R\bRE\bEP\bPO\bOR\bRT\bTS\bS
- If you find a bug in r\bre\bea\bad\bdl\bli\bin\bne\be,\b, you should report it. But
- first, you should make sure that it really is a bug, and
- that it appears in the latest version of the r\bre\bea\bad\bdl\bli\bin\bne\be
- library that you have.
-
- Once you have determined that a bug actually exists, mail
-
-
-
- GNU 1998 Dec 31 17
-
-
-
-
-
- READLINE(3) READLINE(3)
-
-
- a bug report to _\bb_\bu_\bg_\b-_\br_\be_\ba_\bd_\bl_\bi_\bn_\be@_\bg_\bn_\bu_\b._\bo_\br_\bg. If you have a fix,
- you are welcome to mail that as well! Suggestions and
- `philosophical' bug reports may be mailed to _\bb_\bu_\bg_\b-_\br_\be_\ba_\bd_\b-
- _\bl_\bi_\bn_\be@_\bg_\bn_\bu_\b._\bo_\br_\bg or posted to the Usenet newsgroup
- g\bgn\bnu\bu.\b.b\bba\bas\bsh\bh.\b.b\bbu\bug\bg.
-
- Comments and bug reports concerning this manual page
- should be directed to _\bc_\bh_\be_\bt_\b@_\bi_\bn_\bs_\b._\bC_\bW_\bR_\bU_\b._\bE_\bd_\bu.
-
- B\bBU\bUG\bGS\bS
- It's too big and too slow.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GNU 1998 Dec 31 18
-
-
--- 0 ----
From ac131313@cygnus.com Tue Apr 18 19:33:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH/5] Fix dejagnu cleanups
Date: Tue, 18 Apr 2000 19:33:00 -0000
Message-id: <38FD1A8E.CF5F5201@cygnus.com>
X-SW-Source: 2000-04/msg00359.html
Content-length: 765
FYI,
I've committed the attatched.
Andrew
Tue Apr 18 15:49:00 2000 Andrew Cagney <cagney@b1.cygnus.com>
* Makefile.am (SUBDIRS): Add directory example.
* Makefile.in: Re-generate.
Index: Makefile.am
===================================================================
RCS file: /cvs/src/src/dejagnu/Makefile.am,v
retrieving revision 1.1.1.1
diff -p -r1.1.1.1 Makefile.am
*** Makefile.am 1999/11/09 01:28:42 1.1.1.1
--- Makefile.am 2000/04/19 02:02:32
***************
*** 2,8 ****
AUTOMAKE_OPTIONS = cygnus
! SUBDIRS = doc testsuite
# driver script goes in /usr/local/bin
bin_SCRIPTS = runtest
--- 2,8 ----
AUTOMAKE_OPTIONS = cygnus
! SUBDIRS = doc testsuite example
# driver script goes in /usr/local/bin
bin_SCRIPTS = runtest
From ac131313@cygnus.com Tue Apr 18 20:33:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH/5] second attemt at deleting tui/Makefile
Date: Tue, 18 Apr 2000 20:33:00 -0000
Message-id: <38FD28AF.9541FA87@cygnus.com>
X-SW-Source: 2000-04/msg00360.html
Content-length: 1784
Hello,
The attatched (HACK) is my second attempt at eliminating tui/Makefile
from the distribution. The problem comes about because SUBDIRS doesn't
always contain ``tui'' (does it ever?) yet tui/Makefile is always
generated. As the TODO notes. The entire arrangement is up for a
rewrite.
Still, as they say, it works :-(
Andrew
Wed Apr 19 13:06:55 2000 Andrew Cagney <cagney@b1.cygnus.com>
* Makefile.in (distclean): Delete tui/Makefile.
* TODO: Add deletion of tui/Makefile.in to list.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.25.2.1
diff -p -r1.25.2.1 Makefile.in
*** Makefile.in 2000/04/13 05:29:42 1.25.2.1
--- Makefile.in 2000/04/19 03:28:01
*************** distclean: clean
*** 882,887 ****
--- 882,888 ----
rm -f nm.h tm.h xm.h config.status config.h stamp-h .gdbinit
rm -f y.output yacc.acts yacc.tmp y.tab.h
rm -f config.log config.cache
+ rm -f tui/Makefile
rm -f Makefile
maintainer-clean: local-maintainer-clean do-maintainer-clean distclean
Index: TODO
===================================================================
RCS file: /cvs/src/src/gdb/TODO,v
retrieving revision 1.7.2.2
diff -p -r1.7.2.2 TODO
*** TODO 2000/04/14 00:01:26 1.7.2.2
--- TODO 2000/04/19 03:28:03
*************** http://sourceware.cygnus.com/ml/gdb-patc
*** 355,360 ****
--- 355,369 ----
--
+ Eliminate gdb/tui/Makefile.in.
+ Cleanup configury support for optional sub-directories.
+
+ Check how GCC handles multiple front ends for an example of how things
+ could work. A tentative first step is to rationalize things so that
+ all sub directories are handled in a fashion similar to gdb/mi.
+
+ --
+
General Wish List
=================
From ac131313@cygnus.com Tue Apr 18 22:11:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sourceware.cygnus.com, Ian Lance Taylor <ian@zembu.com>
Subject: Re: Problems with snapshot 20000412
Date: Tue, 18 Apr 2000 22:11:00 -0000
Message-id: <38FD3F8C.B30CA4BF@cygnus.com>
References: <200004160807.EAA10378@indy.delorie.com>
X-SW-Source: 2000-04/msg00361.html
Content-length: 864
Eli Zaretskii wrote:
>
> I have few problems with the 20000412 snapshot:
>
> 1) It includes several changes in bfd/doc/Makefile.in which look like
> this:
>
> .texi.dvi:
> - TEXINPUTS=$(top_srcdir)/../texinfo:$$TEXINPUTS \
> + TEXINPUTS=$(top_srcdir)/../texinfo/texinfo.tex:$$TEXINPUTS \
> MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(TEXI2DVI) $<
>
> This change is *wrong*. The TEXINPUTS variable should point to a list
> of directories, not a list of files.
>
> Is it a bug in Automake?
The above definitly comes from automake (both the binutils snap and the
last release (1.4)) and looks very like a bug.
It doesn't appear to affect the build so I don't think there is a reason
to worry about it for 5.0. Poking around the automake perl (?) script it
appears to do a dirname() for some cases but not others.
Andrew
From ac131313@cygnus.com Tue Apr 18 22:58:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>, BINUTILS Patches <binutils@sourceware.cygnus.com>
Subject: src/Makefile.in: Pass down MD5PROG
Date: Tue, 18 Apr 2000 22:58:00 -0000
Message-id: <38FD4AB4.7E58B36E@cygnus.com>
X-SW-Source: 2000-04/msg00362.html
Content-length: 4977
FYI,
I've committed the attatched. It passes MD5PROG down through the
various *.tar.bz2 sub-makes. I could think about some sort of md5 VS
md5sum test but it isn't worth it.
Andrew
Wed Apr 19 12:46:26 2000 Andrew Cagney <cagney@b1.cygnus.com>
* Makefile.in (taz, gdb-taz, gas.tar.bz2, binutils.tar.bz2,
gas+binutils.tar.bz2, libg++.tar.bz2, gnats.tar.bz2, gdb.tar.bz2,
dejagnu.tar.bz2, gdb+dejagnu.tar.bz2, insight.tar.bz2,
insight+dejagnu.tar.bz2, newlib.tar.bz2): Pass MD5PROG to sub-make.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/Makefile.in,v
retrieving revision 1.12.2.1
diff -p -r1.12.2.1 Makefile.in
*** Makefile.in 2000/04/13 02:17:20 1.12.2.1
--- Makefile.in 2000/04/19 05:51:19
*************** PACKAGE = $(TOOL)
*** 1704,1721 ****
--- 1704,1725 ----
taz: $(DEVO_SUPPORT) $(SUPPORT_FILES) texinfo/texinfo.tex
$(MAKE) -f Makefile.in do-proto-toplev \
TOOL=$(TOOL) PACKAGE="$(PACKAGE)" VER="$(VER)" \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(SUPPORT_FILES)"
$(MAKE) -f Makefile.in do-md5sum \
TOOL=$(TOOL) PACKAGE="$(PACKAGE)" VER="$(VER)" \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(SUPPORT_FILES)"
$(MAKE) -f Makefile.in do-tar-bz2 \
TOOL=$(TOOL) PACKAGE="$(PACKAGE)" VER="$(VER)" \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(SUPPORT_FILES)"
.PHONY: gdb-taz
gdb-taz: $(DEVO_SUPPORT) $(SUPPORT_FILES) texinfo/texinfo.tex
$(MAKE) -f Makefile.in taz \
TOOL=$(TOOL) PACKAGE="$(PACKAGE)" VER="$(VER)" \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(SUPPORT_FILES)"
.PHONY: do-proto-toplev
*************** DIST_SUPPORT= $(DEVO_SUPPORT) $(TEXINFO_
*** 1793,1798 ****
--- 1797,1803 ----
GAS_SUPPORT_DIRS= bfd include libiberty opcodes intl setup.com makefile.vms mkdep
gas.tar.bz2: $(DIST_SUPPORT) $(GAS_SUPPORT_DIRS) gas
$(MAKE) -f Makefile.in taz TOOL=gas \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(GAS_SUPPORT_DIRS)"
# The FSF "binutils" release includes gprof and ld.
*************** gas.tar.bz2: $(DIST_SUPPORT) $(GAS_SUPPO
*** 1800,1852 ****
--- 1805,1866 ----
BINUTILS_SUPPORT_DIRS= bfd gas include libiberty opcodes ld gprof intl setup.com makefile.vms mkdep
binutils.tar.bz2: $(DIST_SUPPORT) $(BINUTILS_SUPPORT_DIRS) binutils
$(MAKE) -f Makefile.in taz TOOL=binutils \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(BINUTILS_SUPPORT_DIRS)"
.PHONY: gas+binutils.tar.bz2
GASB_SUPPORT_DIRS= $(GAS_SUPPORT_DIRS) binutils ld gprof
gas+binutils.tar.bz2: $(DIST_SUPPORT) $(GASB_SUPPORT_DIRS) gas
$(MAKE) -f Makefile.in taz TOOL=gas \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(GASB_SUPPORT_DIRS)"
.PHONY: libg++.tar.bz2
LIBGXX_SUPPORT_DIRS=include libstdc++ libio librx libiberty
libg++.tar.bz2: $(DIST_SUPPORT) libg++
$(MAKE) -f Makefile.in taz TOOL=libg++ \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(LIBGXX_SUPPORT_DIRS)"
GNATS_SUPPORT_DIRS=include libiberty send-pr
gnats.tar.bz2: $(DIST_SUPPORT) $(GNATS_SUPPORT_DIRS) gnats
$(MAKE) -f Makefile.in taz TOOL=gnats \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(GNATS_SUPPORT_DIRS)"
.PHONY: gdb.tar.bz2
GDB_SUPPORT_DIRS= bfd include libiberty mmalloc opcodes readline sim utils intl
gdb.tar.bz2: $(DIST_SUPPORT) $(GDB_SUPPORT_DIRS) gdb
$(MAKE) -f Makefile.in gdb-taz TOOL=gdb \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(GDB_SUPPORT_DIRS)"
.PHONY: dejagnu.tar.bz2
DEJAGNU_SUPPORT_DIRS= tcl expect libiberty
dejagnu.tar.bz2: $(DIST_SUPPORT) $(DEJAGNU_SUPPORT_DIRS) dejagnu
$(MAKE) -f Makefile.in taz TOOL=dejagnu \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(DEJAGNU_SUPPORT_DIRS)"
.PHONY: gdb+dejagnu.tar.bz2
GDBD_SUPPORT_DIRS= $(GDB_SUPPORT_DIRS) tcl expect dejagnu
gdb+dejagnu.tar.bz2: $(DIST_SUPPORT) $(GDBD_SUPPORT_DIRS) gdb
$(MAKE) -f Makefile.in gdb-taz TOOL=gdb PACKAGE=gdb+dejagnu \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(GDBD_SUPPORT_DIRS)"
.PHONY: insight.tar.bz2
INSIGHT_SUPPORT_DIRS= $(GDB_SUPPORT_DIRS) tcl tk itcl tix libgui
insight.tar.bz2: $(DIST_SUPPORT) $(GDB_SUPPORT_DIRS) gdb
$(MAKE) -f Makefile.in gdb-taz TOOL=gdb PACKAGE=insight \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(INSIGHT_SUPPORT_DIRS)"
.PHONY: insight+dejagnu.tar.bz2
INSIGHTD_SUPPORT_DIRS= $(INSIGHT_SUPPORT_DIRS) expect dejagnu
insight+dejagnu.tar.bz2: $(DIST_SUPPORT) $(INSIGHTD_SUPPORT_DIRS) gdb
$(MAKE) -f Makefile.in gdb-taz TOOL=gdb PACKAGE="insight+dejagnu" \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(INSIGHTD_SUPPORT_DIRS)"
.PHONY: newlib.tar.bz2
*************** NEWLIB_SUPPORT_DIRS=libgloss
*** 1864,1869 ****
--- 1878,1884 ----
# supports newlib (if only minimally).
newlib.tar.bz2: $(DIST_SUPPORT) $(NEWLIB_SUPPORT_DIRS) newlib
$(MAKE) -f Makefile.in taz TOOL=newlib \
+ MD5PROG="$(MD5PROG)" \
SUPPORT_FILES="$(NEWLIB_SUPPORT_DIRS)" \
DEVO_SUPPORT="$(DEVO_SUPPORT) COPYING.NEWLIB" newlib
From ac131313@cygnus.com Tue Apr 18 23:10:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH/5] src/intl/Makefile.in:distclean additions
Date: Tue, 18 Apr 2000 23:10:00 -0000
Message-id: <38FD4D77.17D83384@cygnus.com>
X-SW-Source: 2000-04/msg00363.html
Content-length: 1836
FYI,
I've committed the attatched to the GDB-5.0 branch but not the trunk.
Its been given the tentative thumbs up by the gettext maintainer.
I'm adding a note to the TODO list on the trunk to make certain that it
does eventually get merged back in.
Andrew
Wed Apr 19 12:37:13 2000 Andrew Cagney <cagney@b1.cygnus.com>
* Makefile.in (distclean): Delete config.status, config.h and
stamp-h.
Index: intl/Makefile.in
===================================================================
RCS file: /cvs/src/src/intl/Makefile.in,v
retrieving revision 1.1.1.1
diff -p -r1.1.1.1 Makefile.in
*** Makefile.in 1999/05/03 07:29:05 1.1.1.1
--- Makefile.in 2000/04/19 06:02:05
***************
*** 1,5 ****
# Makefile for directory with message catalog handling in GNU NLS Utilities.
! # Copyright (C) 1995, 1996, 1997, 1998 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
--- 1,5 ----
# Makefile for directory with message catalog handling in GNU NLS Utilities.
! # Copyright (C) 1995, 1996, 1997, 1998, 2000 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
*************** mostlyclean:
*** 172,178 ****
clean: mostlyclean
distclean: clean
! rm -f Makefile ID TAGS po2msg.sed po2tbl.sed libintl.h config.log
maintainer-clean: distclean
@echo "This command is intended for maintainers to use;"
--- 172,179 ----
clean: mostlyclean
distclean: clean
! rm -f Makefile ID TAGS po2msg.sed po2tbl.sed libintl.h
! rm -f config.log config.status config.h stamp-h
maintainer-clean: distclean
@echo "This command is intended for maintainers to use;"
From ac131313@cygnus.com Tue Apr 18 23:37:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH/5] Re-generate bfd/bfd-in2.h
Date: Tue, 18 Apr 2000 23:37:00 -0000
Message-id: <38FD53B6.FFB153C@cygnus.com>
X-SW-Source: 2000-04/msg00364.html
Content-length: 1412
FYI,
I've committed the attached to the branch. A trunk check-in isn't
necessary (and is left to binutils discretion).
Andrew
Wed Apr 19 16:28:40 2000 Andrew Cagney <cagney@b1.cygnus.com>
* bfd-in2.h: Re-generate.
Index: bfd-in2.h
===================================================================
RCS file: /cvs/src/src/bfd/bfd-in2.h,v
retrieving revision 1.40
diff -p -r1.40 bfd-in2.h
*** bfd-in2.h 2000/04/08 00:10:49 1.40
--- bfd-in2.h 2000/04/19 06:31:06
*************** typedef struct sec
*** 1058,1066 ****
#define SEC_SHARED 0x4000000
/* When a section with this flag is being linked, then if the size of
! the input section is less than a page, it should not cross a page
! boundary. If the size of the input section is one page or more, it
! should be aligned on a page boundary. */
#define SEC_BLOCK 0x8000000
/* Conditionally link this section; do not link if there are no
--- 1058,1066 ----
#define SEC_SHARED 0x4000000
/* When a section with this flag is being linked, then if the size of
! the input section is less than a page, it should not cross a page
! boundary. If the size of the input section is one page or more, it
! should be aligned on a page boundary. */
#define SEC_BLOCK 0x8000000
/* Conditionally link this section; do not link if there are no
From ac131313@cygnus.com Tue Apr 18 23:59:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH/5] More TODO/NEWS cleanups
Date: Tue, 18 Apr 2000 23:59:00 -0000
Message-id: <38FD58F3.48D89606@cygnus.com>
X-SW-Source: 2000-04/msg00365.html
Content-length: 3965
FYI,
I've committed the following. Note that Makefile.in:VERSION defines the
GDB version and not the NEWS file :-)
Andrew
Wed Apr 19 16:37:47 2000 Andrew Cagney <cagney@b1.cygnus.com>
* TODO: Cleanup.
* NEWS: Update GDB version. Duplicate paragraph explaining
obsolete.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.3.2.2
diff -p -r1.3.2.2 NEWS
*** NEWS 2000/04/12 16:55:15 1.3.2.2
--- NEWS 2000/04/19 06:55:38
***************
*** 1,7 ****
What has changed in GDB?
(Organized release by release)
! *** Changes since GDB-4.18:
* Improved support for debugging FP programs on x86 targets
--- 1,7 ----
What has changed in GDB?
(Organized release by release)
! *** Changes in GDB 5.0:
* Improved support for debugging FP programs on x86 targets
*************** Convex c1-*-*, c2-*-*
*** 66,71 ****
--- 66,76 ----
Pyramid pyramid-*-*
ARM RISCix arm-*-* (as host)
Tahoe tahoe-*-*
+
+ Configurations that have been declared obsolete will be commented out,
+ but the code will be left in place. If there is no activity to revive
+ these configurations before the next release of GDB, the sources will
+ be permanently REMOVED.
* New features for SVR4
Index: TODO
===================================================================
RCS file: /cvs/src/src/gdb/TODO,v
retrieving revision 1.7.2.3
diff -p -r1.7.2.3 TODO
*** TODO 2000/04/19 03:37:11 1.7.2.3
--- TODO 2000/04/19 06:55:43
*************** included in the follow-on release.
*** 166,265 ****
--
- GDB 5.0: Test results
- =====================
-
- Please include:
-
- o the output of `config.guess`
- o the date
- o the compiler
- o a note mentioning the reason
- for any serious failures.
-
- --
-
- alpha-dec-osf4.0a, vendor compiler, 2000-03-04
-
- Still has many compile warnings (mostly relating back to PTR vs void*)
- but it did compile using:
-
- CC=cc .../configure
- make
-
- Test results are:
-
- # of expected passes 6223
- # of unexpected failures 103
- # of unexpected successes 2
- # of expected failures 196
- # of unresolved testcases 6
- # of unsupported tests 1
-
- Looking at the output it would appear that GDB is stepping into some
- functions instead of ``next'' ing over them:
-
- 35 dummy();
- (gdb) next
- dummy () at /home/cagney/GDB-DEJAGNU/src/gdb/testsuite/gdb.base/all-types.c:41
- 41 {
-
- Since there is no active maintainer, I'd consider this sufficient for
- 5.0 :-/
-
- --
-
- sparc-sun-solaris2.6, egcs-2.91.66, 2000-02-10
- http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00030.html
-
- There is a SIGTRAP problem that occures in ptrace.exp (Cagney to
- expand on).
-
- # of expected passes 6420
- # of unexpected failures 7
- # of expected failures 199
-
- --
-
- solaris 2.5.1 sparc?, 2.9-gnupro-99r1, 2000-02-10
- http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00032.html
-
- # of expected passes 6420
- # of unexpected failures 6
- # of expected failures 199
-
- --
-
- sparc-unknown-netbsdelf1.4P, egcs-1.1.2+, 2000-03-01
-
- This is with a very recent kernel.
-
- # of expected passes 6055
- # of unexpected failures 88
- # of unexpected successes 1
- # of expected failures 190
- # of unresolved testcases 59
-
- --
-
- GNU/Linux PPC
- http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00185.html
-
- Kevins merged it all in.
-
- --
-
- Unixware
-
- Builds ok. Problems with some of the thread code. Unfortunate but
- not a show stopper. Nick D's still looking at it.
-
- Re: uw-threads issues
- http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00025.html
-
-
------------------------------------------------
-
Code cleanups
=============
--- 166,172 ----
From ac131313@cygnus.com Wed Apr 19 00:13:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: Philippe De Muyter <phdm@macqel.be>, "gdb-patches@sourceware.cygnus.com" <gdb-patches@sourceware.cygnus.com>
Subject: Re: RFA free(NULL) in bcache.c
Date: Wed, 19 Apr 2000 00:13:00 -0000
Message-id: <38FD5B60.F1947FA0@cygnus.com>
References: <200004120905.LAA10853@mail.macqel.be> <npvh1fp7qw.fsf@zwingli.cygnus.com>
X-SW-Source: 2000-04/msg00366.html
Content-length: 107
Jim Blandy wrote:
>
> Yes, please do. Thanks.
Ok :-) I've applied it to the branch and trunk.
Andrew
From ac131313@cygnus.com Wed Apr 19 00:25:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Duffek <nsd@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: sol-thread.c: threads in core files
Date: Wed, 19 Apr 2000 00:25:00 -0000
Message-id: <38FD5F1D.B1DB88B6@cygnus.com>
References: <200004120118.e3C1IYx03766@rtl.cygnus.com>
X-SW-Source: 2000-04/msg00367.html
Content-length: 208
Nick Duffek wrote:
>
> The appended patch fixes a Solaris bug that prevents GDB from seeing
> threads in core files. Credit goes to msnyder for the fix.
FYI,
I've applied this to the 5.0 branch.
Andrew
From ac131313@cygnus.com Wed Apr 19 00:28:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Problems with snapshot 20000412
Date: Wed, 19 Apr 2000 00:28:00 -0000
Message-id: <38FD5FCF.64BFE75D@cygnus.com>
References: <200004160807.EAA10378@indy.delorie.com>
X-SW-Source: 2000-04/msg00368.html
Content-length: 361
Eli Zaretskii wrote:
>
> 2) The diffs include files that AFAIK shouldn't be there:
> dejagnu/example/calc/config.log, dejagnu/example/calc/config.status,
> gdb/tui/Makefile, intl/config.status. I think these files are also
> in md5.sum, which also seems wrong.
FYI, all of these problems should be fixed. Tomorrow's snapshot should
be ok.
Andrew
From eliz@delorie.com Wed Apr 19 00:37:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: jimb@zwingli.cygnus.com
Cc: shebs@apple.com, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: Document RETURN_VALUE_ON_STACK
Date: Wed, 19 Apr 2000 00:37:00 -0000
Message-id: <200004190737.DAA14301@indy.delorie.com>
References: <200004181954.OAA08866@zwingli.cygnus.com> <38FCC3DD.533C7037@apple.com> <npitxfoxew.fsf@zwingli.cygnus.com>
X-SW-Source: 2000-04/msg00369.html
Content-length: 588
From: Jim Blandy <jimb@zwingli.cygnus.com>
Date: 18 Apr 2000 17:29:43 -0500
> + @item RETURN_VALUE_ON_STACK(@var{type})
I think gdbint.texinfo needs to index all the functions and macros it
documents. I know that some victim^H^H^H^H^H^Hvolunteer should go
through the entire file and add the indexing for what's already there,
but there should be no reason to make that job larger.
So could we _please_ start adding such index entries to every new
function/macro/variable we add to the manual? I suggest @findex for
functions and macros and @vindex for variables (if there are any).
From eliz@delorie.com Wed Apr 19 00:45:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com, Ian Lance Taylor <ian@zembu.com>
Subject: Re: Problems with snapshot 20000412
Date: Wed, 19 Apr 2000 00:45:00 -0000
Message-id: <200004190745.DAA14311@indy.delorie.com>
References: <200004160807.EAA10378@indy.delorie.com> <38FD3F8C.B30CA4BF@cygnus.com>
X-SW-Source: 2000-04/msg00370.html
Content-length: 595
> It doesn't appear to affect the build
Really? Did you try renaming your system-wide texinfo.tex (somewhere
in the TeX installation tree)?
The special setting of TEXINPUTS before invoking TeX-related commands
is there to make sure that the manual is produced using the specific
version of texinfo.tex that was used by the maintainer(s), because
another version of texinfo.tex might produce incorrect results or even
fail. If you have the same or compatible version of texinfo.tex in
another place where TeX can find it, you won't see the problems caused
by TEXINPUTS being set incorrectly.
From eliz@delorie.com Wed Apr 19 00:47:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com, Ian Lance Taylor <ian@zembu.com>
Subject: Re: Problems with snapshot 20000412
Date: Wed, 19 Apr 2000 00:47:00 -0000
Message-id: <200004190747.DAA14315@indy.delorie.com>
References: <200004160807.EAA10378@indy.delorie.com> <38FD3F8C.B30CA4BF@cygnus.com>
X-SW-Source: 2000-04/msg00371.html
Content-length: 221
I wrote:
> > It doesn't appear to affect the build
>
> Really? Did you try renaming your system-wide texinfo.tex (somewhere
> in the TeX installation tree)?
Of course, you need also to say "make gdb.dvi" or some such.
From aoliva@cygnus.com Wed Apr 19 00:59:00 2000
From: Alexandre Oliva <aoliva@cygnus.com>
To: binutils@sourceware.cygnus.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: AM33 disassembler: fix for long-standing bug
Date: Wed, 19 Apr 2000 00:59:00 -0000
Message-id: <orzoqqv7ux.fsf@zecarneiro.lsd.ic.unicamp.br>
References: <oritxlkzi4.fsf@zecarneiro.lsd.ic.unicamp.br> <oraeixkz2y.fsf@zecarneiro.lsd.ic.unicamp.br>
X-SW-Source: 2000-04/msg00372.html
Content-length: 223
As written in the previous message, AM30 insns are *not* supposed to
be accepted on AM33. However, I'd still like to install a patch like
this, to keep the platform-detection code identical to that in gas.
Ok to install?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Minor fix to comment in "minsyms.c"
2000-04-18 18:33 Minor fix to comment in "minsyms.c" Guy Harris
@ 2000-04-19 14:13 ` Jim Blandy
0 siblings, 0 replies; 2+ messages in thread
From: Jim Blandy @ 2000-04-19 14:13 UTC (permalink / raw)
To: Guy Harris; +Cc: gdb-patches
Thanks, I've committed this.
> "I see no MSYMBOL_HASH_ADD here." One version of the minsyms hashing
> patch had that macro, but the code in the CVS tree has the
> "add_minsym_to_hash_table()" function instead.
>
> *** /u/guy/src/cmd/gdb-cygnus-cvs/gdb/minsyms.c Tue Apr 18 17:35:37 2000
> --- ./minsyms.c Tue Apr 18 17:55:52 2000
> ***************
> *** 685,691 ****
> MSYMBOL_INFO (msymbol) = info; /* FIXME! */
>
> /* The hash pointers must be cleared! If they're not,
> ! MSYMBOL_HASH_ADD will NOT add this msymbol to the hash table. */
> msymbol->hash_next = NULL;
> msymbol->demangled_hash_next = NULL;
>
> --- 685,691 ----
> MSYMBOL_INFO (msymbol) = info; /* FIXME! */
>
> /* The hash pointers must be cleared! If they're not,
> ! add_minsym_to_hash_table will NOT add this msymbol to the hash table. */
> msymbol->hash_next = NULL;
> msymbol->demangled_hash_next = NULL;
>
>
From jimb@zwingli.cygnus.com Wed Apr 19 14:20:00 2000
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: gdbarchify RETURN_VALUE_ON_STACK
Date: Wed, 19 Apr 2000 14:20:00 -0000
Message-id: <npbt35pz49.fsf@zwingli.cygnus.com>
References: <200004182327.SAA10393@zwingli.cygnus.com> <38FD0067.82067D1E@cygnus.com>
X-SW-Source: 2000-04/msg00382.html
Content-length: 1126
> > 2000-04-17 Jim Blandy <jimb@redhat.com>
> >
> > Bring RETURN_VALUE_ON_STACK under gdbarch's control.
> > * gdbarch.sh (RETURN_VALUE_ON_STACK): New entry.
> > * gdbarch.c, gdbarch.h: Regenerated.
> > * arch-utils.c (default_return_value_on_stack): New function.
> > * arch-utils.h (default_return_value_on_stack): New declaration.
>
> I'd suggest the function name ``generic_return_value_on_stack_not'' (I
> know the name grates) declared as:
> extern gdbarch_return_value_on_stack_ftype ...;
>
> For the arch line, I'd suggest the change:
>
> - f:2:RETURN_VALUE_ON_STACK:int:return_value_on_stack:struct type
> *type:type:::default_return_value_on_stack
> + f:2:RETURN_VALUE_ON_STACK:int:return_value_on_stack:struct type
> *type:type:::default_return_value_on_stack:0
>
> (I think I've set valid_p=0). The generated gdbarch.[hc] will then
> always provide a default. That in turn allowing the #ifndef
> RETURN_VALUE_ON_STACK in values.c to be deleted. Have a look at
> REGISTER_NAME.
>
> After that its ok,
Okay --- I've made these changes, and will commit the result.
From ac131313@cygnus.com Wed Apr 19 16:07:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Alexandre Oliva <aoliva@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: gdbarch IEEE_FLOAT
Date: Wed, 19 Apr 2000 16:07:00 -0000
Message-id: <38FE3BC3.99920D3C@cygnus.com>
References: <200004110302.WAA13962@zwingli.cygnus.com> <38F41405.8F24928@cygnus.com> <np7le0lcjb.fsf@zwingli.cygnus.com> <orln2atjnx.fsf@zecarneiro.lsd.ic.unicamp.br>
X-SW-Source: 2000-04/msg00383.html
Content-length: 689
Alexandre Oliva wrote:
>
> On Apr 14, 2000, Jim Blandy <jimb@zwingli.cygnus.com> wrote:
>
> >> BTW, the need to add the below is going away soon. I've pending
> >> multi-arch patches that will provide this as a non- multi-arch default.
> >>
> >> > + /* Provide a default value for IEEE_FLOAT. */
> >> > + #ifndef IEEE_FLOAT
> >> > + #define IEEE_FLOAT (0)
> >> > + #endif
>
> > Sounds great to me!
>
> BTW, are you aware that gdbarch.c fails to compile on a single-arch
> build whose target header file doesn't define IEEE_FLOAT? For
> example, I've configured --target=mn10300-elf, and gdbarch.c won't
> build because IEEE_FLOAT is not defined.
I believe this was fixed.
Andrew
From ac131313@cygnus.com Wed Apr 19 17:49:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: BINUTILS Patches <binutils@sourceware.cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: Re: Problems with snapshot 20000412
Date: Wed, 19 Apr 2000 17:49:00 -0000
Message-id: <38FE53D4.F249A6FA@cygnus.com>
References: <200004160807.EAA10378@indy.delorie.com> <38FD3F8C.B30CA4BF@cygnus.com> <200004190745.DAA14311@indy.delorie.com> <38FD6E92.8B94D0A0@cygnus.com>
X-SW-Source: 2000-04/msg00384.html
Content-length: 1895
[Mailing lists changed, take care]
Hello,
The automake-000227.tar.bz2 snapshot contains the bug fixed by the
patch:
http://sourceware.cygnus.com/cgi-bin/cvsweb.cgi/automake/automake.in.diff?r1=1.652&r2=1.653&cvsroot=automake
The bug causes bfd/doc/Makefile.in to contain bogus lines like:
.texi.dvi:
TEXINPUTS=$(top_srcdir)/../texinfo/texinfo.tex:$$TEXINPUTS \
MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(TEXI2DVI) $<
(the ``/texinfo.tex'' shouldn't be there). This in turn (as Eli notes
:-) leads to a failed (when there is no pre-installed texinfo.tex) or
broken (when there is) build.
Could I suggest an update to the automake snapshot. Then a fixed
bfd/doc/Makefile.in can be re-generated (gdb-5.0 and binutils-N.NN
branches + trunk).
enjoy,
Andrew
Andrew Cagney wrote:
>
> Eli Zaretskii wrote:
> >
> > > It doesn't appear to affect the build
> >
> > Really? Did you try renaming your system-wide texinfo.tex (somewhere
> > in the TeX installation tree)?
>
> Hmm, ok, yes point taken :-)
>
> > The special setting of TEXINPUTS before invoking TeX-related commands
> > is there to make sure that the manual is produced using the specific
> > version of texinfo.tex that was used by the maintainer(s), because
> > another version of texinfo.tex might produce incorrect results or even
> > fail. If you have the same or compatible version of texinfo.tex in
> > another place where TeX can find it, you won't see the problems caused
> > by TEXINPUTS being set incorrectly.
>
> Its already been reported:
>
> http://sourceware.cygnus.com/ml/bug-automake/1999/msg00007.html
>
> and the follow up:
>
> http://sourceware.cygnus.com/ml/bug-automake/1999/msg00019.html
>
> claims:
>
> > > TEXINPUTS should be a list of directories.
> >
> > Yup, this has been fixed in the CVS tree for quite some time.
>
> I'll double check my automake tools.
>
> Andrew
From jimb@zwingli.cygnus.com Wed Apr 19 18:34:00 2000
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: shebs@apple.com, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: Document RETURN_VALUE_ON_STACK
Date: Wed, 19 Apr 2000 18:34:00 -0000
Message-id: <npya69o8rm.fsf@zwingli.cygnus.com>
References: <200004181954.OAA08866@zwingli.cygnus.com> <38FCC3DD.533C7037@apple.com> <npitxfoxew.fsf@zwingli.cygnus.com> <200004190737.DAA14301@indy.delorie.com>
X-SW-Source: 2000-04/msg00385.html
Content-length: 729
> From: Jim Blandy <jimb@zwingli.cygnus.com>
> Date: 18 Apr 2000 17:29:43 -0500
>
> > + @item RETURN_VALUE_ON_STACK(@var{type})
>
> I think gdbint.texinfo needs to index all the functions and macros it
> documents. I know that some victim^H^H^H^H^H^Hvolunteer should go
> through the entire file and add the indexing for what's already there,
> but there should be no reason to make that job larger.
>
> So could we _please_ start adding such index entries to every new
> function/macro/variable we add to the manual? I suggest @findex for
> functions and macros and @vindex for variables (if there are any).
I think we should be using @deftypefn for everything; that will build
a function index for us automatically. No?
From ac131313@cygnus.com Wed Apr 19 21:23:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: gdbarch IEEE_FLOAT
Date: Wed, 19 Apr 2000 21:23:00 -0000
Message-id: <38FE85F2.5472031@cygnus.com>
References: <200004110302.WAA13962@zwingli.cygnus.com> <38F41405.8F24928@cygnus.com> <np7le0lcjb.fsf@zwingli.cygnus.com> <38FA86D1.2E4CB93D@cygnus.com> <npu2gzp7hf.fsf@zwingli.cygnus.com>
X-SW-Source: 2000-04/msg00386.html
Content-length: 818
Jim Blandy wrote:
>
> > > > > + /* Provide a default value for IEEE_FLOAT. */
> > > > > + #ifndef IEEE_FLOAT
> > > > > + #define IEEE_FLOAT (0)
> > > > > + #endif
> > >
> > > Sounds great to me!
> >
> > BTW, is the default ``0'' or ``1''? The above has zero, but for
> > multi-arch it is set to one. (Just let me know, I'll tweek it when I
> > remove it :-).
>
> Well, for old targets it has to be zero.
>
> I was thinking that, for new gdbarch-style targets, 1 was the more
> convenient default, but on more careful reflection, I'm not sure
> that's smart: if someone is converting an existing port to gdbarch, it
> would be very confusing for IEEE_FLOAT to suddenly change its default
> value.
>
> So the default should be zero.
Everyone multi-arching please note. I've just committed this change.
Andrew
From ac131313@cygnus.com Wed Apr 19 21:25:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [RFC] Cleanup (TARGET_BFD_VMA_BIT, IEEE_FLOAT, CALL_DUMMY_WORDS and SIZEOF_CALL_DUMMY_WORDS
Date: Wed, 19 Apr 2000 21:25:00 -0000
Message-id: <38FE8668.719EEF2C@cygnus.com>
References: <38FA8EF2.BC8ACBFD@cygnus.com>
X-SW-Source: 2000-04/msg00387.html
Content-length: 1085
Andrew Cagney wrote:
>
> Hello,
>
> The attatched patch does to several multi-arch variables what my
> previous patch did to functions. It changes gdbarch.h so that it
> provides the default for both the multi-arch and non- multi-arch cases.
>
> (It isn't final as I need info from JimB)
>
> I'll look to apply it in a few days once the last patch has settled
> down.
>
> Andrew
>
> ------------------------------------------------------------------------
> Mon Apr 17 13:37:10 2000 Andrew Cagney <cagney@b1.cygnus.com>
>
> * gdbarch.sh: Make multi-arch variable defaults, defaults for non-
> multi-arch targets.
> (TARGET_BFD_VMA_BIT, IEEE_FLOAT, CALL_DUMMY_WORDS,
> SIZEOF_CALL_DUMMY_WORDS): Update.
>
> * inferior.h (CALL_DUMMY_WORDS, SIZEOF_CALL_DUMMY_WORDS): Default
> provided by gdbarch.
> (CALL_DUMMY_P): Add FIXME. gdbarch should provide default.
>
> * valprint.c (IEEE_FLOAT): Default provided by gdbarch.
I've committed this change to the trunk. IEEE_FLOAT is zero by default.
Andrew
From ac131313@cygnus.com Thu Apr 20 01:09:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [RFC] Convert STACK_ALIGN to multi-arch ....
Date: Thu, 20 Apr 2000 01:09:00 -0000
Message-id: <38FEBAE3.D0FD616D@cygnus.com>
X-SW-Source: 2000-04/msg00388.html
Content-length: 9322
Hello,
The attached patch converts the STACK_ALIGN macro into a multi-arch
runtime test/call. What was:
#ifdef STACK_ALIGN
x = STACK_ALIGN (x)
#endif
becomes
if (STACK_ALIGN_P ())
x = STACK_ALIGN (x);
The need for a predicate becomes clear if you look at valops.c. How it
handles all the possible compatibility cases is pretty confusing so I'll
quickly go through each case I thought of:
!multi-arch && !defined (STACK_ALIGN)
A legacy system that doesn't define STACK_ALIGN.
STACK_ALIGN_P() is defined as gdbarch_stack_align_p()
which will always return 0 (the stack_align function is
never set).
STACK_ALIGN() is defined as gdbarch_stack_align() which
keeps things compiling.
!multi-arch && defined (STACK_ALIGN)
Legacy system providing STACK_ALIGN macro in tm.h.
multi-arch && defined (STACK_ALIGN)
Hybrid system (ex d10v) providing STACK_ALIGN macro in tm.h.
That legacy #ifdef STACK_ALIGN in gdbarch.h forces
STACK_ALIGN_P() to 1.
multi-arch && !defined (STACK_ALIGN)
normal case.
Both STACK_ALIGN_P() and STACK_ALIGN() are mapped
onto functions like any other gdbarch case.
can anyone think of any other cases (did I get these cases right :-)?
Other thoughts.
Andrew
Thu Apr 20 14:35:46 2000 Andrew Cagney <cagney@b1.cygnus.com>
* valops.c (hand_function_call): Replace #ifdef STACK_ALIGN with
run-time test for STACK_ALIGN_P.
* gdbarch.sh: Add support for function and variable predicates.
(STACK_ALIGN): Add. Implement with predicate - STACK_ALIGN_P.
Index: gdbarch.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.c,v
retrieving revision 1.14
diff -p -r1.14 gdbarch.c
*** gdbarch.c 2000/04/20 04:24:03 1.14
--- gdbarch.c 2000/04/20 07:49:16
*************** struct gdbarch
*** 213,218 ****
--- 213,219 ----
gdbarch_frame_locals_address_ftype *frame_locals_address;
gdbarch_saved_pc_after_call_ftype *saved_pc_after_call;
gdbarch_frame_num_args_ftype *frame_num_args;
+ gdbarch_stack_align_ftype *stack_align;
};
*************** struct gdbarch startup_gdbarch = {
*** 317,322 ****
--- 318,324 ----
0,
0,
0,
+ 0,
/* startup_gdbarch() */
};
struct gdbarch *current_gdbarch = &startup_gdbarch;
*************** verify_gdbarch (struct gdbarch *gdbarch)
*** 620,625 ****
--- 622,628 ----
if ((GDB_MULTI_ARCH >= 2)
&& (gdbarch->frame_num_args == 0))
internal_error ("gdbarch: verify_gdbarch: frame_num_args invalid");
+ /* Skip verify of stack_align, has predicate */
}
*************** gdbarch_dump (void)
*** 955,960 ****
--- 958,967 ----
"gdbarch_update: FRAME_NUM_ARGS = 0x%08lx\n",
(long) current_gdbarch->frame_num_args
/*FRAME_NUM_ARGS ()*/);
+ fprintf_unfiltered (gdb_stdlog,
+ "gdbarch_update: STACK_ALIGN = 0x%08lx\n",
+ (long) current_gdbarch->stack_align
+ /*STACK_ALIGN ()*/);
}
struct gdbarch_tdep *
*************** set_gdbarch_frame_num_args (struct gdbar
*** 2485,2490 ****
--- 2492,2520 ----
gdbarch_frame_num_args_ftype frame_num_args)
{
gdbarch->frame_num_args = frame_num_args;
+ }
+
+ int
+ gdbarch_stack_align_p (struct gdbarch *gdbarch)
+ {
+ return gdbarch->stack_align != 0;
+ }
+
+ CORE_ADDR
+ gdbarch_stack_align (struct gdbarch *gdbarch, CORE_ADDR sp)
+ {
+ if (gdbarch->stack_align == 0)
+ internal_error ("gdbarch: gdbarch_stack_align invalid");
+ if (gdbarch_debug >= 2)
+ fprintf_unfiltered (gdb_stdlog, "gdbarch_stack_align called\n");
+ return gdbarch->stack_align (sp);
+ }
+
+ void
+ set_gdbarch_stack_align (struct gdbarch *gdbarch,
+ gdbarch_stack_align_ftype stack_align)
+ {
+ gdbarch->stack_align = stack_align;
}
Index: gdbarch.h
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.h,v
retrieving revision 1.10
diff -p -r1.10 gdbarch.h
*** gdbarch.h 2000/04/20 04:24:04 1.10
--- gdbarch.h 2000/04/20 07:49:19
*************** extern void set_gdbarch_frame_num_args (
*** 798,803 ****
--- 798,820 ----
#endif
#endif
+ #if defined (STACK_ALIGN)
+ /* Legacy for systems yet to multi-arch STACK_ALIGN */
+ #define STACK_ALIGN_P() (1)
+ #endif
+
+ extern int gdbarch_stack_align_p (struct gdbarch *gdbarch);
+ #if (GDB_MULTI_ARCH > 1) || !defined (STACK_ALIGN_P)
+ #define STACK_ALIGN_P() (gdbarch_stack_align_p (current_gdbarch))
+ #endif
+
+ typedef CORE_ADDR (gdbarch_stack_align_ftype) (CORE_ADDR sp);
+ extern CORE_ADDR gdbarch_stack_align (struct gdbarch *gdbarch, CORE_ADDR sp);
+ extern void set_gdbarch_stack_align (struct gdbarch *gdbarch, gdbarch_stack_align_ftype *stack_align);
+ #if (GDB_MULTI_ARCH > 1) || !defined (STACK_ALIGN)
+ #define STACK_ALIGN(sp) (gdbarch_stack_align (current_gdbarch, sp))
+ #endif
+
extern struct gdbarch_tdep *gdbarch_tdep (struct gdbarch *gdbarch);
Index: valops.c
===================================================================
RCS file: /cvs/src/src/gdb/valops.c,v
retrieving revision 1.10
diff -p -r1.10 valops.c
*** valops.c 2000/04/17 02:27:37 1.10
--- valops.c 2000/04/20 07:49:30
*************** You must use a pointer to function type
*** 1534,1547 ****
arg_type = check_typedef (VALUE_ENCLOSING_TYPE (args[i]));
len = TYPE_LENGTH (arg_type);
! #ifdef STACK_ALIGN
! /* MVS 11/22/96: I think at least some of this stack_align code is
! really broken. Better to let PUSH_ARGUMENTS adjust the stack in
! a target-defined manner. */
! aligned_len = STACK_ALIGN (len);
! #else
! aligned_len = len;
! #endif
if (INNER_THAN (1, 2))
{
/* stack grows downward */
--- 1534,1547 ----
arg_type = check_typedef (VALUE_ENCLOSING_TYPE (args[i]));
len = TYPE_LENGTH (arg_type);
! if (STACK_ALIGN_P ())
! /* MVS 11/22/96: I think at least some of this
! stack_align code is really broken. Better to let
! PUSH_ARGUMENTS adjust the stack in a target-defined
! manner. */
! aligned_len = STACK_ALIGN (len);
! else
! aligned_len = len;
if (INNER_THAN (1, 2))
{
/* stack grows downward */
*************** You must use a pointer to function type
*** 1583,1594 ****
if (struct_return)
{
int len = TYPE_LENGTH (value_type);
! #ifdef STACK_ALIGN
! /* MVS 11/22/96: I think at least some of this stack_align code is
! really broken. Better to let PUSH_ARGUMENTS adjust the stack in
! a target-defined manner. */
! len = STACK_ALIGN (len);
! #endif
if (INNER_THAN (1, 2))
{
/* stack grows downward */
--- 1583,1593 ----
if (struct_return)
{
int len = TYPE_LENGTH (value_type);
! if (STACK_ALIGN_P ())
! /* MVS 11/22/96: I think at least some of this stack_align
! code is really broken. Better to let PUSH_ARGUMENTS adjust
! the stack in a target-defined manner. */
! len = STACK_ALIGN (len);
if (INNER_THAN (1, 2))
{
/* stack grows downward */
*************** You must use a pointer to function type
*** 1609,1619 ****
hppa_push_arguments */
#ifndef NO_EXTRA_ALIGNMENT_NEEDED
- #if defined(STACK_ALIGN)
/* MVS 11/22/96: I think at least some of this stack_align code is
really broken. Better to let PUSH_ARGUMENTS adjust the stack in
a target-defined manner. */
! if (INNER_THAN (1, 2))
{
/* If stack grows down, we must leave a hole at the top. */
int len = 0;
--- 1608,1617 ----
hppa_push_arguments */
#ifndef NO_EXTRA_ALIGNMENT_NEEDED
/* MVS 11/22/96: I think at least some of this stack_align code is
really broken. Better to let PUSH_ARGUMENTS adjust the stack in
a target-defined manner. */
! if (STACK_ALIGN_P () && INNER_THAN (1, 2))
{
/* If stack grows down, we must leave a hole at the top. */
int len = 0;
*************** You must use a pointer to function type
*** 1624,1630 ****
len += CALL_DUMMY_STACK_ADJUST;
sp -= STACK_ALIGN (len) - len;
}
- #endif /* STACK_ALIGN */
#endif /* NO_EXTRA_ALIGNMENT_NEEDED */
sp = PUSH_ARGUMENTS (nargs, args, sp, struct_return, struct_addr);
--- 1622,1627 ----
*************** You must use a pointer to function type
*** 1642,1649 ****
sp = PUSH_RETURN_ADDRESS (real_pc, sp);
#endif /* PUSH_RETURN_ADDRESS */
! #if defined(STACK_ALIGN)
! if (!INNER_THAN (1, 2))
{
/* If stack grows up, we must leave a hole at the bottom, note
that sp already has been advanced for the arguments! */
--- 1639,1645 ----
sp = PUSH_RETURN_ADDRESS (real_pc, sp);
#endif /* PUSH_RETURN_ADDRESS */
! if (STACK_ALIGN_P () && !INNER_THAN (1, 2))
{
/* If stack grows up, we must leave a hole at the bottom, note
that sp already has been advanced for the arguments! */
*************** You must use a pointer to function type
*** 1651,1657 ****
sp += CALL_DUMMY_STACK_ADJUST;
sp = STACK_ALIGN (sp);
}
- #endif /* STACK_ALIGN */
/* XXX This seems wrong. For stacks that grow down we shouldn't do
anything here! */
--- 1647,1652 ----
From ac131313@cygnus.com Thu Apr 20 01:30:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [RFC] Convert d10v's STACK_ALIGN; Was: [RFC] Convert STACK_ALIGN to multi-arch ....
Date: Thu, 20 Apr 2000 01:30:00 -0000
Message-id: <38FEBFF2.DCB46367@cygnus.com>
References: <38FEBAE3.D0FD616D@cygnus.com>
X-SW-Source: 2000-04/msg00389.html
Content-length: 1934
Hello,
The attatched is a follow-on to the previous STACK_ALIGN patch. It
updates the d10v.
Andrew
Thu Apr 20 18:15:08 2000 Andrew Cagney <cagney@b1.cygnus.com>
* d10v-tdep.c (d10v_gdbarch_init): Initialize stack_align.
(d10v_stack_align): Make static.
* config/d10v/tm-d10v.h (STACK_ALIGN): Delete.
Index: d10v-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/d10v-tdep.c,v
retrieving revision 1.2
diff -p -r1.2 d10v-tdep.c
*** d10v-tdep.c 2000/02/09 04:46:47 1.2
--- d10v-tdep.c 2000/04/20 08:25:38
*************** d10v_frame_chain_valid (chain, frame)
*** 104,110 ****
return ((chain) != 0 && (frame) != 0 && (frame)->pc > IMEM_START);
}
! CORE_ADDR
d10v_stack_align (CORE_ADDR len)
{
return (len + 1) & ~1;
--- 104,110 ----
return ((chain) != 0 && (frame) != 0 && (frame)->pc > IMEM_START);
}
! static CORE_ADDR
d10v_stack_align (CORE_ADDR len)
{
return (len + 1) & ~1;
*************** d10v_gdbarch_init (info, arches)
*** 1655,1660 ****
--- 1655,1661 ----
set_gdbarch_frame_locals_address (gdbarch, d10v_frame_locals_address);
set_gdbarch_saved_pc_after_call (gdbarch, d10v_saved_pc_after_call);
set_gdbarch_frame_num_args (gdbarch, frame_num_args_unknown);
+ set_gdbarch_stack_align (gdbarch, d10v_stack_align);
return gdbarch;
}
Index: config/d10v/tm-d10v.h
===================================================================
RCS file: /cvs/src/src/gdb/config/d10v/tm-d10v.h,v
retrieving revision 1.2
diff -p -r1.2 tm-d10v.h
*** tm-d10v.h 2000/02/09 04:46:47 1.2
--- tm-d10v.h 2000/04/20 08:25:38
***************
*** 25,31 ****
extern int d10v_register_sim_regno (int reg);
#define REGISTER_SIM_REGNO(NR) d10v_register_sim_regno((NR))
- extern CORE_ADDR d10v_stack_align (CORE_ADDR size);
- #define STACK_ALIGN(SIZE) (d10v_stack_align (SIZE))
-
#define NO_EXTRA_ALIGNMENT_NEEDED 1
--- 25,28 ----
From eliz@delorie.com Thu Apr 20 02:24:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: jimb@cygnus.com
Cc: shebs@apple.com, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: Document RETURN_VALUE_ON_STACK
Date: Thu, 20 Apr 2000 02:24:00 -0000
Message-id: <200004200924.FAA15717@indy.delorie.com>
References: <200004181954.OAA08866@zwingli.cygnus.com> <38FCC3DD.533C7037@apple.com> <npitxfoxew.fsf@zwingli.cygnus.com> <200004190737.DAA14301@indy.delorie.com> <npya69o8rm.fsf@zwingli.cygnus.com>
X-SW-Source: 2000-04/msg00390.html
Content-length: 456
> From: Jim Blandy <jimb@cygnus.com>
> Date: 19 Apr 2000 20:34:21 -0500
>
> I think we should be using @deftypefn for everything; that will build
> a function index for us automatically. No?
If that's what people prefer, I don't mind.
Personally, I dislike the @defXXX commands, because they violate the
Texinfo language rules (e.g., use unescaped braces). Their handling
in makeinfo is a horrible kludge which has subtle problems and
idiosyncrasies.
From ac131313@cygnus.com Thu Apr 20 02:56:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Philippe De Muyter <phdm@macqel.be>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: PATCH/RFA free(NULL) bomb in printcmd.c
Date: Thu, 20 Apr 2000 02:56:00 -0000
Message-id: <38FED326.69E89A2B@cygnus.com>
References: <200004110900.LAA01874@mail.macqel.be>
X-SW-Source: 2000-04/msg00391.html
Content-length: 1288
Philippe De Muyter wrote:
>
> Andrew Cagney wrote :
> > Um, I'm confused. wouldn't it be easier to just delete the two cleanup
> > calls (the first, perhaphs, replaced with make_cleanup (null_cleanup,
> > NULL))?
>
> Of course. But I did not know if the number of cleanups mattered, so I made
> my change as small as possible.
>
> [ 10 minutes reflexion and search ]
>
> The current situation and my and your `fixes' would have caused memory leaks,
> because the intention of the programmer there was actually to `free (name)'
> and `free (filename)', but `make_cleanup' is called before `name' and `filename'
> are allocated.
> I now think I have the correct fix. OK to commit ?
>
> Philippe De Muyter <phdm@macqel.be>
>
> * printcmd.c (print_address_symbolic): Call `make_cleanup' with
> `(free_current_contents, &x)', not `(free, x)'.
> * utils.c (free_current_contents): Do not `free (NULL)'.
FYI,
Something wierd is going on. For the d10v-elf target, FreeBSD 3.4
host. I see the regression:
x/d &oct
0x2007dc0: -1490098887
gdb in free(): warning: junk pointer, too high to make sense.
(gdb) FAIL: gdb.base/long_long.exp: x/d &oct
The warning appears all over the place. It suggests that something is
corrupting one of those pointers.
Andrew
From ac131313@cygnus.com Thu Apr 20 03:31:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Philippe De Muyter <phdm@macqel.be>, gdb-patches@sourceware.cygnus.com
Subject: Re: PATCH/RFA free(NULL) bomb in printcmd.c
Date: Thu, 20 Apr 2000 03:31:00 -0000
Message-id: <38FEDC0A.F915966C@cygnus.com>
References: <200004110900.LAA01874@mail.macqel.be> <38FED326.69E89A2B@cygnus.com>
X-SW-Source: 2000-04/msg00392.html
Content-length: 4051
Andrew Cagney wrote:
> > Philippe De Muyter <phdm@macqel.be>
> >
> > * printcmd.c (print_address_symbolic): Call `make_cleanup' with
> > `(free_current_contents, &x)', not `(free, x)'.
> > * utils.c (free_current_contents): Do not `free (NULL)'.
>
> FYI,
>
> Something wierd is going on. For the d10v-elf target, FreeBSD 3.4
> host. I see the regression:
>
> x/d &oct
> 0x2007dc0: -1490098887
> gdb in free(): warning: junk pointer, too high to make sense.
> (gdb) FAIL: gdb.base/long_long.exp: x/d &oct
>
> The warning appears all over the place. It suggests that something is
> corrupting one of those pointers.
The attached appears to work much better. The function wasn't cleaning
up when build_address_symbolic failed. This led to a later cleanup call
freeing a garbage pointer on the stack.
Philippe, can you try it on your platform.
Andrew
Thu Apr 20 17:39:11 2000 Andrew Cagney <cagney@b1.cygnus.com>
* defs.h, utils.c (free_current_contents): Change parameter to
void*.
From Philippe De Muyter <phdm@macqel.be>:
* printcmd.c (print_address_symbolic): Call `make_cleanup' with
`(free_current_contents, &x)', not `(free, x)'.
* utils.c (free_current_contents): Do not `free (NULL)'.
* printcmd.c (print_address_symbolic): Cleanup after a failed
call to build_address_symbolic.
Index: defs.h
===================================================================
RCS file: /cvs/src/src/gdb/defs.h,v
retrieving revision 1.13
diff -p -r1.13 defs.h
*** defs.h 2000/03/30 18:54:28 1.13
--- defs.h 2000/04/20 10:17:47
*************** extern void restore_cleanups (struct cle
*** 354,360 ****
extern void restore_final_cleanups (struct cleanup *);
extern void restore_my_cleanups (struct cleanup **, struct cleanup *);
! extern void free_current_contents (char **);
extern void null_cleanup (void *);
--- 354,360 ----
extern void restore_final_cleanups (struct cleanup *);
extern void restore_my_cleanups (struct cleanup **, struct cleanup *);
! extern void free_current_contents (void *);
extern void null_cleanup (void *);
Index: printcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/printcmd.c,v
retrieving revision 1.3
diff -p -r1.3 printcmd.c
*** printcmd.c 2000/04/04 04:16:48 1.3
--- printcmd.c 2000/04/20 10:17:54
*************** print_address_symbolic (addr, stream, do
*** 562,573 ****
int offset = 0;
int line = 0;
! struct cleanup *cleanup_chain = make_cleanup (free, name);
! if (print_symbol_filename)
! make_cleanup (free, filename);
if (build_address_symbolic (addr, do_demangle, &name, &offset, &filename, &line, &unmapped))
! return;
fputs_filtered (leadin, stream);
if (unmapped)
--- 562,576 ----
int offset = 0;
int line = 0;
! /* throw away both name and filename */
! struct cleanup *cleanup_chain = make_cleanup (free_current_contents, &name);
! make_cleanup (free_current_contents, &filename);
if (build_address_symbolic (addr, do_demangle, &name, &offset, &filename, &line, &unmapped))
! {
! do_cleanups (cleanup_chain);
! return;
! }
fputs_filtered (leadin, stream);
if (unmapped)
Index: utils.c
===================================================================
RCS file: /cvs/src/src/gdb/utils.c,v
retrieving revision 1.6
diff -p -r1.6 utils.c
*** utils.c 2000/03/30 18:54:28 1.6
--- utils.c 2000/04/20 10:17:59
*************** restore_my_cleanups (pmy_chain, chain)
*** 375,384 ****
to arrange to free the object thus allocated. */
void
! free_current_contents (location)
! char **location;
{
! free (*location);
}
/* Provide a known function that does nothing, to use as a base for
--- 375,385 ----
to arrange to free the object thus allocated. */
void
! free_current_contents (void *ptr)
{
! void **location = ptr;
! if (*location != NULL)
! free (*location);
}
/* Provide a known function that does nothing, to use as a base for
From ac131313@cygnus.com Thu Apr 20 04:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Tim Mooney <mooney@dogbert.cc.ndsu.nodak.edu>
Cc: "Daniel Berlin+gnu.gdb.bug" <dan@cgsoftware.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA]: Fix crashing bug in set follow-fork-mode
Date: Thu, 20 Apr 2000 04:00:00 -0000
Message-id: <38FEE2A9.E83C0059@cygnus.com>
References: <Pine.OSF.4.21.0004162124380.31138-100000@dogbert.cc.ndsu.nodak.edu>
X-SW-Source: 2000-04/msg00393.html
Content-length: 2902
Tim Mooney wrote:
>
> >Someone please commit this to the branch if it gets approved.
> >I have no idea how to make a testcase for it.
> >I knew something screwy was up when "set follow-fork-mode parent" said
> >"ambiguous command: \"parent\"", and it clearly wasn't ambiguous at
> >all.
> >So, i looked, and it had trashed our stack, and thought we had 6
> >million matches, rather than one.
>
> scheduler-lock seems to have the same problem (see the enum at line 765 of
> infrun.c). Conditions under which it happens are the exact same as in my
> report for the follow-fork-mode problem. I've left the patch to fix the
> problem for you or someone else, since it's again very small.
Thanks!
I've applied the attatched to the 5.0 branch and trunk. Anyone come up
with a testsuite addition to add to the trunk?
Andrew
Thu Apr 20 18:54:15 2000 Andrew Cagney <cagney@b1.cygnus.com>
From Daniel Berlin <dan@cgsoftware.com> and Tim Mooney
<mooney@dogbert.cc.ndsu.nodak.edu>:
* infrun.c (follow_fork_mode_kind_names): NULL terminate
array. Re-indent.
(scheduler_enums): Ditto.
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.7
diff -p -r1.7 infrun.c
*** infrun.c 2000/04/13 10:22:22 1.7
--- infrun.c 2000/04/20 10:32:34
*************** static int follow_vfork_when_exec;
*** 436,448 ****
static char *follow_fork_mode_kind_names[] =
{
! /* ??rehrauer: The "both" option is broken, by what may be a 10.20
! kernel problem. It's also not terribly useful without a GUI to
! help the user drive two debuggers. So for now, I'm disabling
! the "both" option.
! "parent", "child", "both", "ask" };
! */
! "parent", "child", "ask"};
static char *follow_fork_mode_string = NULL;
\f
--- 436,448 ----
static char *follow_fork_mode_kind_names[] =
{
! /* ??rehrauer: The "both" option is broken, by what may be a 10.20
! kernel problem. It's also not terribly useful without a GUI to
! help the user drive two debuggers. So for now, I'm disabling the
! "both" option. */
! /* "parent", "child", "both", "ask" */
! "parent", "child", "ask", NULL
! };
static char *follow_fork_mode_string = NULL;
\f
*************** static char schedlock_on[] = "on";
*** 762,768 ****
static char schedlock_step[] = "step";
static char *scheduler_mode = schedlock_off;
static char *scheduler_enums[] =
! {schedlock_off, schedlock_on, schedlock_step};
static void
set_schedlock_func (char *args, int from_tty, struct cmd_list_element *c)
--- 762,773 ----
static char schedlock_step[] = "step";
static char *scheduler_mode = schedlock_off;
static char *scheduler_enums[] =
! {
! schedlock_off,
! schedlock_on,
! schedlock_step,
! NULL
! };
static void
set_schedlock_func (char *args, int from_tty, struct cmd_list_element *c)
From dan@cgsoftware.com Thu Apr 20 09:48:00 2000
From: dan@cgsoftware.com (Daniel Berlin+list.gdb-patches)
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Tim Mooney <mooney@dogbert.cc.ndsu.nodak.edu>, "Daniel Berlin+gnu.gdb.bug" <dan@cgsoftware.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA]: Fix crashing bug in set follow-fork-mode
Date: Thu, 20 Apr 2000 09:48:00 -0000
Message-id: <d7nk3ehd.fsf@dan.resnet.rochester.edu>
References: <Pine.OSF.4.21.0004162124380.31138-100000@dogbert.cc.ndsu.nodak.edu> <38FEE2A9.E83C0059@cygnus.com>
X-SW-Source: 2000-04/msg00394.html
Content-length: 696
Andrew Cagney <ac131313@cygnus.com> writes:
I have a better idea.
I just made it check the enum list, when the command is added, like
so:
while(1)
{
if enumlist[i]==0
break (this means it's properly null terminated)
if (!isalnum(enumlist[i][0]))
internal_error("<command name>'s enum list is not null
terminated, or contains non-alphanumeric characters.");
i++;
}
This is better than the testsuite addition, because if you screw up,
gdb won't start, or it'll crash (it depends on where enumlist[i][0] is
located.)
Watch:
bash-2.03# ./gdb -nw
gdb-internal-error: follow-fork-mode has non-null terminated enum list, or non alpha-numeric character in enum list
bash-2.03#
Patch attached
From law@cygnus.com Thu Apr 20 10:20:00 2000
From: Jeffrey A Law <law@cygnus.com>
To: Alexandre Oliva <aoliva@cygnus.com>
Cc: binutils@sourceware.cygnus.com, gdb-patches@sourceware.cygnus.com
Subject: Re: AM33 disassembler: fix for long-standing bug
Date: Thu, 20 Apr 2000 10:20:00 -0000
Message-id: <5434.956247166@upchuck>
References: <orzoqqv7ux.fsf@zecarneiro.lsd.ic.unicamp.br>
X-SW-Source: 2000-04/msg00395.html
Content-length: 650
In message < orzoqqv7ux.fsf@zecarneiro.lsd.ic.unicamp.br >you write:
> --=-=-=
>
> As written in the previous message, AM30 insns are *not* supposed to
> be accepted on AM33. However, I'd still like to install a patch like
> this, to keep the platform-detection code identical to that in gas.
> Ok to install?
>
>
> --=-=-=
> Content-Type: text/x-patch
> Content-Disposition: inline; filename=am33-opcodes-fix.patch
>
> Index: opcodes/ChangeLog
> by Alexandre Oliva <aoliva@cygnus.com>
>
> * m10300-dis.c (HAVE_AM30, HAVE_AM33): Define.
> (disassemble): Use them.
This is fine. Please install it.
jeff
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-04-19 14:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-04-18 18:33 Minor fix to comment in "minsyms.c" Guy Harris
2000-04-19 14:13 ` Jim Blandy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox