From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43716@debbugs.gnu.org
Subject: bug#43716: 28.0.50; Error with emacsclient <file>:
Date: Wed, 30 Sep 2020 16:30:12 +0200 [thread overview]
Message-ID: <87r1qje3rf.fsf@gnu.org> (raw)
In-Reply-To: <874knfeofw.fsf@gnu.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It's unfortunate that there's no way to get Emacs to reliably give a
> backtrace -- I'm guessing there's a condition-case somewhere in the
> server code that inhibits the debugging?
Possibly.
> Does
>
> (setq debug-ignored-errors nil
> debug-on-error t)
>
> help with getting a backtrace? (It's a long shot...)
>
> (setq debug-on-message "arguments")
>
> may allow the backtrace to appear in some circumstances.
Neither of those seems to work for this specific issue. :-(
>> Starting program: /home/horn/Repos/el/emacs/lib-src/emacsclient ~/tmp/test.aux
>> Waiting for Emacs...
>> *ERROR*: Wrong number of arguments: (1 . 4), 5
>
> I grepped for the string "*ERROR*" in the Emacs source tree, and
> couldn't find it, but perhaps it's composed differently.
I found it. :-)
lib-src/emacsclient.c
2095 fprintf (stderr, "*ERROR*: %s", str);
>> [Inferior 1 (process 23487) exited with code 01]
>> (gdb) bt
>> No stack.
>>
>> Any help? My GDB foo is quite low but I can operate it when given
>> instructions.
>
> Setting a breakpoint on Fsignal could perhaps work? My gdb-foo is
> low, too, though.
Hm, I come there at least 5 times when "emacsclient file" is run. I've
looked at "bt", especially the lisp backtraces but those contained just
(error ...) or (signal ...) forms wheras I guess the error I get must
come from funcall or so...
Bye,
Tassilo
next prev parent reply other threads:[~2020-09-30 14:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:03 bug#43716: 28.0.50; Error with emacsclient <file>: Tassilo Horn
2020-09-30 13:03 ` Lars Ingebrigtsen
2020-09-30 13:58 ` Tassilo Horn
2020-09-30 14:07 ` Lars Ingebrigtsen
2020-09-30 14:27 ` Eli Zaretskii
2020-09-30 14:38 ` Tassilo Horn
2020-09-30 14:54 ` Eli Zaretskii
2020-09-30 14:30 ` Tassilo Horn [this message]
2020-09-30 14:50 ` Lars Ingebrigtsen
2020-09-30 15:51 ` Tassilo Horn
2020-09-30 17:08 ` Tassilo Horn
2020-10-01 15:33 ` Tassilo Horn
2020-10-01 3:30 ` Lars Ingebrigtsen
2020-09-30 17:59 ` Noam Postavsky
2020-09-30 18:10 ` Lars Ingebrigtsen
2020-09-30 14:42 ` Andreas Schwab
2020-09-30 14:40 ` Andreas Schwab
2020-09-30 14:44 ` Tassilo Horn
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=87r1qje3rf.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=43716@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).