view BUGS @ 93765:e08b610ba485

(gdb): New group. (gdb-debug-log-max, gdb-enable-debug) (gdb-cpp-define-alist-program, gdb-cpp-define-alist-flags) (gdb-show-main, gdb-many-windows, gdb-use-separate-io-buffer) (gdb-speedbar-auto-raise, gdb-use-colon-colon-notation) (gdb-show-changed-values, gdb-max-children) (gdb-delete-out-of-scope, gdb-same-frame, gdb-find-source-frame) (breakpoint-enabled, breakpoint-disabled, gdb-max-frames) (gdb-all-registers, gdb-memory-repeat-count, gdb-memory-format) (gdb-memory-unit): Move to new group from GUD group. (menu): Allow customization from GDB-UI menu-item.

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
make sure it isn't a known issue.