XXX Work around GDB breaking SIGFPE handling

For some reason when I have GDB attached, SIGFPE is not processed correctly. Even if I run this in gdb: handle SIGFPE nostop handle SIGFPE noprint
AustinWise · Jul 6, 2024 · f9f5886 · f9f5886
1 parent e270bbe
commit f9f5886
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/src/coreclr/nativeaot/Runtime.Base/src/System/Runtime/ExceptionHandling.cs b/src/coreclr/nativeaot/Runtime.Base/src/System/Runtime/ExceptionHandling.cs
@@ -606,6 +606,7 @@ public static void RhThrowHwEx(uint exceptionCode, ref ExInfo exInfo)
                     // We don't wrap SEH exceptions from foreign code like CLR does, so we believe that we
                     // know the complete set of HW faults generated by managed code and do not need to handle
                     // this case.
+                    Internal.Console.WriteLine($"Unexpected HwExceptionCode: {exceptionCode}");
                     FailFastViaClasslib(RhFailFastReason.InternalError, null, faultingCodeAddress);
                     break;
             }

diff --git a/src/coreclr/pal/src/thread/context.cpp b/src/coreclr/pal/src/thread/context.cpp
@@ -1303,6 +1303,10 @@ DWORD CONTEXTGetExceptionCodeForSignal(const siginfo_t *siginfo,
         case SIGFPE:
             switch (siginfo->si_code)
             {
+                case 0:
+                    // XXX: is this actually a good idea?
+                    // For some reason we see this when a gdb is attached.
+                    return EXCEPTION_INT_DIVIDE_BY_ZERO;
                 case FPE_INTDIV:
                     return EXCEPTION_INT_DIVIDE_BY_ZERO;
                 case FPE_INTOVF: