view BUGS @ 47443:b2fb48df4f9f

(gud-gdb-massage-args, gud-sdb-massage-args) (gud-pdb-massage-args): Delete. (gdb, sdb, pdb): Don't pass gud-*-massage-args any more. (gud-gdb-command-name): New var. Put "--fullname" in there. (gud-query-cmdline): Use the most recent executable as the default. Don't add "--fullname" (it's only valid/meaningful for GDB). (gud-xdb-marker-filter): Use match-string. (gud-perldb-massage-args): Don't add "-d". (gud-perldb-command-name): Add "-d". (gud-common-init): If `massage-args' is nil, don't call it. (gud-format-command): Don't hardcode point-min==1.

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 P in Emacs) to
make sure it isn't a known issue.