procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; * etc/DEBUG: Add a section about debugging native-compilation.

Browse source
This commit is contained in:
Eli Zaretskii 2021-10-14 12:14:14 +03:00
parent 8153f70b9c
commit 74deafe921
1 changed files with 22 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

31
etc/DEBUG
View file

@ -573,6 +573,28 @@ debugging did not (yet) happen. Here are some useful techniques for that:
GET_FROM_IMAGE for displaying an image, etc. See 'enum it_method' in GET_FROM_IMAGE for displaying an image, etc. See 'enum it_method' in
dispextern.h for the full list of values. dispextern.h for the full list of values.
** Debugging problems with native-compiled Lisp.
When you encounter problems specific to native-compilation of Lisp, we
recommend to follow the procedure below to try to identify the cause:
. Reduce the problematic .el file to the minimum by bisection, and
try identifying the function that causes the problem.
. Reduce the problematic function to the minimal code that still
reproduces the problem.
. Study the problem's artifacts, like Lisp or C backtraces, to try
identifying the cause of the problem.
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 names ELNFILENAME_libgccjit_repro.c, where ELNFILENAME is the
name of the problematic .eln file, in the same directory where the
.eln file is produced. Then attach that reproducer C file to your bug
report.
** Following longjmp call. ** Following longjmp call.
Recent versions of glibc (2.4+?) encrypt stored values for setjmp/longjmp which Recent versions of glibc (2.4+?) encrypt stored values for setjmp/longjmp which
@ -875,15 +897,6 @@ It is also useful to look at the corrupted object or data structure in
a fresh Emacs session and compare its contents with a session that you a fresh Emacs session and compare its contents with a session that you
are debugging. are debugging.
** Debugging problems with non-ASCII characters
If you experience problems which seem to be related to non-ASCII
characters, such as \201 characters appearing in the buffer or in your
files, set the variable byte-debug-flag to t. This causes Emacs to do
some extra checks, such as look for broken relations between byte and
character positions in buffers and strings; the resulting diagnostics
might pinpoint the cause of the problem.
** Debugging the TTY (non-windowed) version ** Debugging the TTY (non-windowed) version
The most convenient method of debugging the character-terminal display The most convenient method of debugging the character-terminal display