Re: Reporting Lisp errors in dynamic modules

[Eli Zaretskii]

> From: Philipp Stephani <address@hidden>
> Date: Fri, 27 Nov 2015 18:40:39 +0000
> Cc: address@hidden, address@hidden, address@hidden, 
>       address@hidden
> 
> OK, here's a quick (untested, sorry) patch.

Thanks, I pushed it.

It indeed broke 2 tests from test.el; I fixed that.

(Please don't forget to provide ChangeLog style log messages.)

After this change, the backtrace in my original use case is still
somewhat unusual:

  Debugger entered--Lisp error: (wrong-type-argument integerp "1")
    internal--module-call(#<save-value <pointer 00fdab30> <unused> <unused> 
<unused>> ("1" 2))
    mod-test-sum("1" 2)
    eval((mod-test-sum "1" 2) nil)
    elisp--eval-last-sexp(nil)
    eval-last-sexp(nil)
    funcall-interactively(eval-last-sexp nil)
    call-interactively(eval-last-sexp nil nil)
    command-execute(eval-last-sexp)

But I guess we could live with that for now.  (If someone has ideas
how to remove the "save-value" part and unwrap the list of arguments
so it looks like in the preceding line, please tell.)