* bug#66912: With `require', the byte compiler reports the wrong file for errors. @ 2023-11-03 11:32 Alan Mackenzie 2023-11-03 16:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 0 siblings, 1 reply; 8+ messages in thread From: Alan Mackenzie @ 2023-11-03 11:32 UTC (permalink / raw) To: 66912; +Cc: Stefan Monnier Hello, Emacs. When byte compiling file1, and file1 requires file2, should there be an error in file2, it is reported as being in file1, at the requires line. This is entirely unhelpful; the reported position should be that of the error in file2. Things get even more unhelpful if there is a nesting of required files, and the error occurs in a deeply nested file. For an example, create the files ~/test-byte-compile-errors.el: ######################################################################### ;; -*- lexical-binding:t -*- (require 'test-byte-compile-errors-2 "~/test-byte-compile-errors-2") ######################################################################### , and ~/test-byte-compile-errors-2.el: ######################################################################### ;; -*- lexical-binding:t -*- (defvar foo nil) (defun bar () (setq foo)) ; <================== (provide 'test-byte-compile-errors-2) ######################################################################### .. From an Emacs session, do M-x byte-compile-file RET ~/test-byte-compile-errors.el RET .. This will report the error as Compiling file /home/acm/test-byte-compile-errors.el at Fri Nov 3 10:14:40 2023 test-byte-compile-errors.el:2:2: Error: Wrong number of arguments: setq, 1 .. This is not the error location. ######################################################################### Preliminary analysis: The pertinent error information is discarded by one of two condition-cases in the macro displaying-byte-compile-warnings in emacs-lisp/bytecomp.el. If these condition-case's are disabled (for example by spiking the enclosing `if' forms) and the necessary defuns recompiled, there instead appears an error message in the display area. On setting debug-on-error to t and repeating the compilation, one gets a backtrace, which whilst not ideal, is considerably more helpful than the original error message. This appears to be a fundamental problem with condition-case. When an error occurs, the stack gets unwound before the error handlers have a chance to analyse it. -- Alan Mackenzie (Nuremberg, Germany). ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-03 11:32 bug#66912: With `require', the byte compiler reports the wrong file for errors Alan Mackenzie @ 2023-11-03 16:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 16:30 ` Alan Mackenzie 0 siblings, 1 reply; 8+ messages in thread From: Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-11-03 16:09 UTC (permalink / raw) To: Alan Mackenzie; +Cc: 66912 > The pertinent error information is discarded by one of two > condition-cases in the macro displaying-byte-compile-warnings in > emacs-lisp/bytecomp.el. Kind of, yes. But the info available there is hard to use: basically at that point we could get the error message and the backtrace, which is what we get when we set `byte-compile-debug`. In the case where `byte-compile-debug` is not set, we don't really want to display a backtrace, so we'd have to "analyze" that backtrace to try and extract a useful error message from it, which is hard&brittle. > If these condition-case's are disabled (for example by spiking the > enclosing `if' forms) By "spiking" do you mean setting `byte-compile-debug`? > This appears to be a fundamental problem with condition-case. When an > error occurs, the stack gets unwound before the error handlers have a > chance to analyse it. [ This is going a bit on a tangent, but I think it would be good to add some support for something like Common-Lisp's `handler-bind`, i.e. error handlers that are run before unwinding the stack (so they can capture the stack trace as well as the value of dynbound vars at the moment the error occurs, for example). It would make it possible for ERT to refrain from activating `debug-on-error`, for example (which it does in order to capture the backtrace at the time of the error). ] I think for this specific problem being discussed (which is indeed a fairly common occurrence in my experience), the better solution is to change `load` so it adds the "context" (i.e. filename and ideally also the approximate file position info) to errors. [ This may require something like `handler-bind`. ] Stefan ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-03 16:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-11-12 16:30 ` Alan Mackenzie 2023-11-12 17:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 0 siblings, 1 reply; 8+ messages in thread From: Alan Mackenzie @ 2023-11-12 16:30 UTC (permalink / raw) To: Stefan Monnier; +Cc: acm, 66912 Hello, Stefan. On Fri, Nov 03, 2023 at 12:09:03 -0400, Stefan Monnier wrote: > > The pertinent error information is discarded by one of two > > condition-cases in the macro displaying-byte-compile-warnings in > > emacs-lisp/bytecomp.el. > Kind of, yes. But the info available there is hard to use: basically at > that point we could get the error message and the backtrace, which is > what we get when we set `byte-compile-debug`. In the case where > `byte-compile-debug` is not set, we don't really want to display > a backtrace, .... Why not? We're not in the compilation any more, we're loading a file. Some error has prevented that file loading, so we want a backtrace just as we would get with M-x load-file foo.elc RET. > .... so we'd have to "analyze" that backtrace to try and extract a > useful error message from it, which is hard&brittle. Indeed, so. > > If these condition-case's are disabled (for example by spiking the > > enclosing `if' forms) > By "spiking" do you mean setting `byte-compile-debug`? I actually commented out byte-compile-debug, replacing it with t. But same idea, yes. > > This appears to be a fundamental problem with condition-case. When an > > error occurs, the stack gets unwound before the error handlers have a > > chance to analyse it. > [ This is going a bit on a tangent, but I think it would be good to add > some support for something like Common-Lisp's `handler-bind`, > i.e. error handlers that are run before unwinding the stack (so they > can capture the stack trace as well as the value of dynbound vars at > the moment the error occurs, for example). > It would make it possible for ERT to refrain from activating > `debug-on-error`, for example (which it does in order to capture the > backtrace at the time of the error). ] That sounds kind of useful. > I think for this specific problem being discussed (which is indeed > a fairly common occurrence in my experience), the better solution is to > change `load` so it adds the "context" (i.e. filename and ideally also > the approximate file position info) to errors. > [ This may require something like `handler-bind`. ] Another solution would be to dispense with display-byte-compile-warnings, just letting compiler errors generate backtraces. The problem here is that there is no distinction in bytecomp.el between "external" errors (such as from require) and errors detected by the compiler in the source file being compiled. The first decidedly want a backtrace, the second probably not. All these errors are handled as though they were "internal" errors detected by the compiler. This is suboptimal. Perhaps we should report the second type of error (detected by the compiler) by calling a warning function, as we do for warnings, and removing the damaging condition-case's as suggested two paragraphs back. > Stefan -- Alan Mackenzie (Nuremberg, Germany). ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-12 16:30 ` Alan Mackenzie @ 2023-11-12 17:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 20:41 ` Alan Mackenzie 0 siblings, 1 reply; 8+ messages in thread From: Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-11-12 17:28 UTC (permalink / raw) To: Alan Mackenzie; +Cc: 66912 > Why not? We're not in the compilation any more, we're loading a file. > Some error has prevented that file loading, so we want a backtrace just > as we would get with M-x load-file foo.elc RET. Hmm... that's a good point. >> I think for this specific problem being discussed (which is indeed >> a fairly common occurrence in my experience), the better solution is to >> change `load` so it adds the "context" (i.e. filename and ideally also >> the approximate file position info) to errors. >> [ This may require something like `handler-bind`. ] > Another solution would be to dispense with > display-byte-compile-warnings, just letting compiler errors generate > backtraces. > > The problem here is that there is no distinction in bytecomp.el between > "external" errors (such as from require) and errors detected by the > compiler in the source file being compiled. These are two fairly "clear" cases, admittedly. But there are also cases in between where it's less clear, mostly with errors during macro-expansion where the internal/external distinction is not always that clear since some macros come from outside but others come from the very file we're compiling, and where we can't easily tell if an error is due to a bug in the macro definition or a bug in the use of the macro. > The first decidedly want a backtrace, the second probably not. > All these errors are handled as though they were "internal" errors > detected by the compiler. This is suboptimal. Also there are 2 questions: - whether to give a backtrace (and/or enter the debugger). - when we don't show a backtrace, what info do we put in the error message. For the first, the current "solution" is to set `byte-compile-debug`. It's not ideal, and we should improve it, but at least we do have a solution for it. For the second we currently don't show a good enough info and in my previous response I focused on that part. > Perhaps we should report the second type of error (detected by the > compiler) by calling a warning function, as we do for warnings, and > removing the damaging condition-case's as suggested two paragraphs back. If the user is not asking to see backtraces, the current treatment seems cleaner than without any `condition-case`. So maybe those `condition-case` should be turned into `condition-case-unless-debug`? Stefan ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-12 17:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-11-12 20:41 ` Alan Mackenzie 2023-11-12 21:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 0 siblings, 1 reply; 8+ messages in thread From: Alan Mackenzie @ 2023-11-12 20:41 UTC (permalink / raw) To: Stefan Monnier; +Cc: acm, 66912 Hello, Stefan. On Sun, Nov 12, 2023 at 12:28:13 -0500, Stefan Monnier wrote: > > Why not? We're not in the compilation any more, we're loading a file. > > Some error has prevented that file loading, so we want a backtrace just > > as we would get with M-x load-file foo.elc RET. > Hmm... that's a good point. > >> I think for this specific problem being discussed (which is indeed > >> a fairly common occurrence in my experience), the better solution is to > >> change `load` so it adds the "context" (i.e. filename and ideally also > >> the approximate file position info) to errors. > >> [ This may require something like `handler-bind`. ] > > Another solution would be to dispense with > > display-byte-compile-warnings, just letting compiler errors generate > > backtraces. > > The problem here is that there is no distinction in bytecomp.el between > > "external" errors (such as from require) and errors detected by the > > compiler in the source file being compiled. > These are two fairly "clear" cases, admittedly. > But there are also cases in between where it's less clear, mostly with > errors during macro-expansion where the internal/external distinction is > not always that clear since some macros come from outside but others > come from the very file we're compiling, and where we can't easily tell > if an error is due to a bug in the macro definition or a bug in the use > of the macro. Question: will the user be able to identify the macro and its source file if we just print the bare error message as enforced by displaying-byte-compile-warnings? It the answer is no or not really, we should give her the backtrace to get started on. > > The first decidedly want a backtrace, the second probably not. > > All these errors are handled as though they were "internal" errors > > detected by the compiler. This is suboptimal. > Also there are 2 questions: > - whether to give a backtrace (and/or enter the debugger). > - when we don't show a backtrace, what info do we put in the error message. > For the first, the current "solution" is to set `byte-compile-debug`. > It's not ideal, and we should improve it, but at least we do have > a solution for it. I suspect byte-compile-debug isn't widely known. Its name is also a bit discordant - it's not necessarily about debugging byte-compile, it's just to get sensible error messages when something goes wrong, especially when that something is not part of the byte compiler. > For the second we currently don't show a good enough info and in my > previous response I focused on that part. Indeed, for the error message which provoked this bug report, the current information is poor indeed. Considering that require's can be nested, we only tell the user the identity of the outermost one. > > Perhaps we should report the second type of error (detected by the > > compiler) by calling a warning function, as we do for warnings, and > > removing the damaging condition-case's as suggested two paragraphs back. > If the user is not asking to see backtraces, the current treatment seems > cleaner than without any `condition-case`. It's "neat and tidy", but at the cost of discarding all useful information. There are other common situations in Emacs where the debugger is entered, or a backtrace output without debug-on-error having to be set. Perhaps this one should join them. > So maybe those `condition-case` should be turned into > `condition-case-unless-debug`? I think this would be a very useful first step. I think it likely a user will set debug-on-error on encountering any unhelpful error message. > Stefan -- Alan Mackenzie (Nuremberg, Germany). ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-12 20:41 ` Alan Mackenzie @ 2023-11-12 21:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 23:00 ` Drew Adams 2024-10-29 18:59 ` Alan Mackenzie 0 siblings, 2 replies; 8+ messages in thread From: Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-11-12 21:19 UTC (permalink / raw) To: Alan Mackenzie; +Cc: 66912 >> But there are also cases in between where it's less clear, mostly with >> errors during macro-expansion where the internal/external distinction is >> not always that clear since some macros come from outside but others >> come from the very file we're compiling, and where we can't easily tell >> if an error is due to a bug in the macro definition or a bug in the use >> of the macro. > > Question: will the user be able to identify the macro and its source > file if we just print the bare error message as enforced by > displaying-byte-compile-warnings? I think we print a "bare" error message (together with the location of the macro call). Often it's good enough (e.g. when the error is really in the macro call itself). Sometimes it's very perplexing :-( > It the answer is no or not really, we should give her the backtrace to > get started on. Says the one who claimed earlier that backtraces are stressful :-) Dumping the backtrace is a kind of cop-out. Don't get me wrong, I love backtraces, but I don't think we should blissfully throw backtraces at unsuspecting users (unlike Python, say). IOW, we should first work harder to provide better error messages. >> For the first, the current "solution" is to set `byte-compile-debug`. >> It's not ideal, and we should improve it, but at least we do have >> a solution for it. > > I suspect byte-compile-debug isn't widely known. Its name is also a bit > discordant - it's not necessarily about debugging byte-compile, it's > just to get sensible error messages when something goes wrong, > especially when that something is not part of the byte compiler. Agreed. >> For the second we currently don't show a good enough info and in my >> previous response I focused on that part. > Indeed, for the error message which provoked this bug report, the > current information is poor indeed. Considering that require's can be > nested, we only tell the user the identity of the outermost one. We don't even give that info. We just give the line number of the `require`. It's almost as good as the outermost file name, but not quite. > It's "neat and tidy", but at the cost of discarding all useful > information. There are other common situations in Emacs where > the debugger is entered, or a backtrace output without debug-on-error > having to be set. Hmm... I can't think of such a situation. When/where do we show a backtrace without the user's explicit request? >> So maybe those `condition-case` should be turned into >> `condition-case-unless-debug`? > I think this would be a very useful first step. I think it likely a > user will set debug-on-error on encountering any unhelpful error > message. AFAICT this would basically be equivalent to aliasing `byte-compile-debug` to `debug-on-error`. It may turn out to be annoying occasionally, but I think it's worth a try (I've never found it useful to have `byte-compile-debug` set to t without also setting `debug-on-error` to t). Stefan ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-12 21:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-11-12 23:00 ` Drew Adams 2024-10-29 18:59 ` Alan Mackenzie 1 sibling, 0 replies; 8+ messages in thread From: Drew Adams @ 2023-11-12 23:00 UTC (permalink / raw) To: Stefan Monnier, Alan Mackenzie; +Cc: 66912@debbugs.gnu.org > Dumping the backtrace is a kind of cop-out. > > Don't get me wrong, I love backtraces, but I don't think we should > blissfully throw backtraces at unsuspecting users (unlike Python, say). > IOW, we should first work harder to provide better error messages. OT, so ... sorry. It just occurred to me that instead of just having a Boolean `debug-on-error', which turns use of the debugger on/off for an error, there might be a third possibility: show an error message and let you then decide whether to open the backtrace -- maybe click (or `RET') the error msg, or in some other way make the choice. IOW, we could perhaps prepare a backtrace buffer without actually entering its recursive edit etc. If a user doesn't ask to see/use it then it just sits there (buried) as an unused buffer. Or display of the error msg could allow for (1) activating/entering the backtrace buffer, (2) leaving it buried, or (3) deleting it. No idea about implementation or reasonableness. Just something that occurred to me. Yes, first priority should be a good error msg. Yes, users should be able to optionally open the debugger. But could we maybe give them that possibility after showing the error msg? ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#66912: With `require', the byte compiler reports the wrong file for errors. 2023-11-12 21:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 23:00 ` Drew Adams @ 2024-10-29 18:59 ` Alan Mackenzie 1 sibling, 0 replies; 8+ messages in thread From: Alan Mackenzie @ 2024-10-29 18:59 UTC (permalink / raw) To: Stefan Monnier; +Cc: acm, 66912 Hello, Stefan. It's been almost a year since this bug got lost in the storm of other things which needed doing. I'd like to come back to it now. To refresh your memory, the problem was about not getting any information about foo when an error occurred during (require 'foo). And no apologies for the top posting, which just seems appropriate, since new possibilities (handler-bind in particular, thanks!) have appeared in the last year. My latest idea is to put (the C equivalent of) handler-bind around the readevalloop call near the end of Fload. So with my test files from last year, in place of the current error output test-byte-compile-errors.el:2:11: Error: Wrong type argument: listp, baz the following line would appear: test-byte-compile-errors.el:2:11: While loading "test-byte-compile-errors-2.el" Error: Wrong type argument: listp, baz .. The "While loading "foo.el" " bit would be repeated as needed for nested (require 'foo)s. OK, the error line could be quite long, but the information would at least be there. This could surely be achieved with something like the following in Fload: (handler-bind ((lambda (err) (signal (car err) (combine-error-info "While loading " file (cdr err))))) readevalloop (Qget_file_char, &input, hist_file_name, 0, Qnil, Qnil, Qnil, Qnil);) (where, obviously, the details need to be worked out). It would need augmenting with handling for (eq debug-on-error t), and probably a few other things, too. What do you think of the idea? -- Alan Mackenzie (Nuremberg, Germany). On Sun, Nov 12, 2023 at 16:19:36 -0500, Stefan Monnier wrote: > >> But there are also cases in between where it's less clear, mostly with > >> errors during macro-expansion where the internal/external distinction is > >> not always that clear since some macros come from outside but others > >> come from the very file we're compiling, and where we can't easily tell > >> if an error is due to a bug in the macro definition or a bug in the use > >> of the macro. > > Question: will the user be able to identify the macro and its source > > file if we just print the bare error message as enforced by > > displaying-byte-compile-warnings? > I think we print a "bare" error message (together with the location of > the macro call). Often it's good enough (e.g. when the error is really > in the macro call itself). Sometimes it's very perplexing :-( > > It the answer is no or not really, we should give her the backtrace to > > get started on. > Says the one who claimed earlier that backtraces are stressful :-) > Dumping the backtrace is a kind of cop-out. > Don't get me wrong, I love backtraces, but I don't think we should > blissfully throw backtraces at unsuspecting users (unlike Python, say). > IOW, we should first work harder to provide better error messages. > >> For the first, the current "solution" is to set `byte-compile-debug`. > >> It's not ideal, and we should improve it, but at least we do have > >> a solution for it. > > I suspect byte-compile-debug isn't widely known. Its name is also a bit > > discordant - it's not necessarily about debugging byte-compile, it's > > just to get sensible error messages when something goes wrong, > > especially when that something is not part of the byte compiler. > Agreed. > >> For the second we currently don't show a good enough info and in my > >> previous response I focused on that part. > > Indeed, for the error message which provoked this bug report, the > > current information is poor indeed. Considering that require's can be > > nested, we only tell the user the identity of the outermost one. > We don't even give that info. We just give the line number of the > `require`. It's almost as good as the outermost file name, but not quite. > > It's "neat and tidy", but at the cost of discarding all useful > > information. There are other common situations in Emacs where > > the debugger is entered, or a backtrace output without debug-on-error > > having to be set. > Hmm... I can't think of such a situation. When/where do we show > a backtrace without the user's explicit request? > >> So maybe those `condition-case` should be turned into > >> `condition-case-unless-debug`? > > I think this would be a very useful first step. I think it likely a > > user will set debug-on-error on encountering any unhelpful error > > message. > AFAICT this would basically be equivalent to aliasing > `byte-compile-debug` to `debug-on-error`. > It may turn out to be annoying occasionally, but I think it's worth > a try (I've never found it useful to have `byte-compile-debug` set to > t without also setting `debug-on-error` to t). > Stefan ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2024-10-29 18:59 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2023-11-03 11:32 bug#66912: With `require', the byte compiler reports the wrong file for errors Alan Mackenzie 2023-11-03 16:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 16:30 ` Alan Mackenzie 2023-11-12 17:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 20:41 ` Alan Mackenzie 2023-11-12 21:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors 2023-11-12 23:00 ` Drew Adams 2024-10-29 18:59 ` Alan Mackenzie
Code repositories for project(s) associated with this external index https://git.savannah.gnu.org/cgit/emacs.git https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.