GNU bug report logs - #43716
28.0.50; Error with emacsclient <file>:

Previous Next

Package: emacs;

Reported by: Tassilo Horn <tsdh <at> gnu.org>

Date: Wed, 30 Sep 2020 07:04:01 UTC

Severity: normal

Found in version 28.0.50

Done: Tassilo Horn <tsdh <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Tassilo Horn <tsdh <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, 43716 <at> debbugs.gnu.org
Subject: bug#43716: 28.0.50; Error with emacsclient <file>:
Date: Wed, 30 Sep 2020 16:38:33 +0200
Eli Zaretskii <eliz <at> gnu.org> writes:

>> It's unfortunate that there's no way to get Emacs to reliably give a
>> backtrace
>
> I thought debug-on-event and SIGUSR1/SIGUSR2 were such a way?

More details, please.  I mean, it's set to sigusr2 by default and I get
a *Backtrace* buffer with "kill -SIGUSR2 <emacs_pid>".  But how does
that help with the "emacsclient <file>" invocation?

Anyway, I'm sure you know where I have to set a breakpoint in order to
find out where and for which function "Wrong number of arguments" is
signalled, right?

Bye,
Tassilo





This bug report was last modified 4 years and 291 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.