bug#36648: emacs signals under gdb - [Re: connecting to a lost server process

[Eli Zaretskii]

> Date: Thu, 18 Jul 2019 20:28:21 +0530 (IST)
> Cc: 36648@debbugs.gnu.org
> From: Madhu <enometh@meer.net>
> 
> >From the point of view of elisp, no error should be signalled - it
> should be caught by the condition-case.

You called those functions directly, from outside of the Lisp machine,
so the condition-case machinery is not working.

> However there seems to be room for improvement around the "abort when
> awaiting for input behaviour" - as there are other situations within
> gdb which are not "really" error situations which unnecessarily abort
> emacs.

There are inherent difficulties that require this behavior, sorry.

> M-x gud-gdb RET
> gdb --args emacs --arg -Q --eval '(progn (load-library "custom") 
> (load-library "server") (setq server-name "emacs-test"))' RET
> 
> =>
> 
> |Reading symbols from emacs...
> (gdb) show args
> Argument list to give program being debugged when it is started is "--arg -Q 
> --eval \'\(progn \(load-library custom \) \(load-library server \) \(setq 
> server-name emacs-test \)\)\'".

I suggest to use "M-x gdb", not "M-x gud-gdb".  The latter is an old
and semi-deprecated way of running GDB from Emacs.

I guess we can close this bug report?