On 2016-08-06 06:02, Eli Zaretskii wrote:
>> Cc: emacs-devel@gnu.org
>> From: Clément Pit--Claudel <clement.pit@gmail.com>
>> Date: Fri, 5 Aug 2016 11:38:14 -0400
>>
>> On 2016-08-05 09:40, Eli Zaretskii wrote:
>>> But with -daemon, even the first invocation of emacsclient already 
>>> doesn't display the backtrace, right?  So there's still something 
>>> different between these two use cases.
>>
>> Well, it depends what you mean by "display the backtrace": the server doesn't respect debug-on-error
> 
> Why doesn't it?  Isn't that already a bug?

I think you confirmed that it was in the other "Backtraces on server?" thread?

>> but if I register my own debugger, then I *can* capture the first backtrace. I have attached a file cpc-server.el that will explain the issue better than I can explain it in words (thanks for your patience!). Here's how it's used:
> 
> So you are saying that the problem is the daemon doesn't increment
> num-nonmacro-input-events for each new connection?  That should be
> easy enough to fix, isn't it?

Yes, but I fear it wouldn't cover the following case:

(condition-case err1 
    (condition-case err2
        (error "A")
      (error (error "B)))
  (error (message "Oups")))

Only the first error would be captured by the debugger.

Clément.