From 38fdeaef4654d4d4fac8c73f48058d94f158e711 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Tue, 23 Nov 2021 16:25:48 +0200 Subject: [PATCH] ; * etc/DEBUG: Fix last change. --- etc/DEBUG | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/etc/DEBUG b/etc/DEBUG index ced6a92d711..a05aeef1606 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -591,10 +591,13 @@ If you cannot figure out the cause for the problem using the above, native-compile the problematic file after setting the variable 'comp-libgccjit-reproducer' to a non-nil value. That should produce a file named ELNFILENAME_libgccjit_repro.c, where ELNFILENAME is the -name of the problematic .eln file in the same directory where the .eln -file is produced, or a file repro.c under your ~/.emacs.d/eln-cache -(which one depends on how the native-compilation is invoked). Then -attach that reproducer C file to your bug report. +name of the problematic .eln file, either in the same directory where +the .eln file is produced, or under your ~/.emacs.d/eln-cache (which +one depends on how the native-compilation is invoked). It is also +possible that the reproducer file's name will be something like +subr--trampoline-XXXXXXX_FUNCTION_libgccjit_repro.c, where XXXXXXX is +a long string of hex digits and FUNCTION is some function from the +compiled .el file. Attach that reproducer C file to your bug report. ** Following longjmp call. -- 2.39.2