docs: update known-issues

1 files changed, 21 insertions, 3 deletions

diff --git a/docs/known-issues.txt b/docs/known-issues.txt
index 95e19919..b7874799 100644
--- a/docs/known-issues.txt
+++ b/docs/known-issues.txt
@@ -102,10 +102,10 @@ Symptoms:
     libtool.m4: error: problem compiling FC test program
 
 Explanations:
-  The gc build procedure tries to run a Fortran test to see if it has a
+  The gcc build procedure tries to run a Fortran test to see if it has a
   working native fortran compiler installed on the build machine, and it
-  can't find one. A native Fortran compielr is needed (seems to be) to
-  build the Fortran frontend of the cross-compiler.
+  can't find one. A native Fortran compiler is needed (seems to be neede)
+  to build the Fortran frontend of the cross-compiler.
   Even if you don't want to build the Fortran frontend, gcc tries to see
   if it has one, but fails. This is no problem, as the Fortran frontend
   will not be built. There is nothing to be worry about (unless you do
@@ -119,3 +119,21 @@ Workaround:
   None needed, it's a spurious error.
 
 --------------------------------
+Symptoms:
+  gcc barfs because it is "unable to detect the exception model".
+
+Explanations:
+  On some architectures, proper stack unwinding (C++) requires that
+  setjmp/longjmp (sjlj) be used, while on other architectures do not
+  need sjlj. On some architectures, gcc is unable to determine whether
+  sjlj are needed or not.
+
+Fix:
+  None so far.
+
+Workaround:
+  Trying setting use of sjlj to either 'Y' or 'N' (instead of the
+  default 'M') in the menuconfig, option CT_CC_GCC_SJLJ_EXCEPTIONS
+  labelled "Use sjlj for exceptions".
+
+--------------------------------