From: Eli Zaretskii <eliz@gnu.org>
To: Madhu <enometh@meer.net>
Cc: 36648@debbugs.gnu.org
Subject: bug#36648: emacs signals under gdb - [Re: connecting to a lost server process
Date: Thu, 18 Jul 2019 18:24:54 +0300 [thread overview]
Message-ID: <838ssvwek9.fsf@gnu.org> (raw)
In-Reply-To: <20190718.202821.1196946470014157934.enometh@meer.net> (message from Madhu on Thu, 18 Jul 2019 20:28:21 +0530 (IST))
> 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?
next prev parent reply other threads:[~2019-07-18 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190712062057.15599.qmail@localhost.localdomain>
[not found] ` <83r26v3cy3.fsf@gnu.org>
[not found] ` <mailman.985.1562918079.2688.help-gnu-emacs@gnu.org>
2019-07-14 12:00 ` bug#36648: emacs signals under gdb - [Re: connecting to a lost server process Madhu
2019-07-18 5:35 ` Eli Zaretskii
2019-07-18 14:58 ` Madhu
2019-07-18 15:24 ` Eli Zaretskii [this message]
2019-07-19 1:53 ` Madhu
2019-07-19 6:53 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838ssvwek9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36648@debbugs.gnu.org \
--cc=enometh@meer.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).