aboutsummaryrefslogtreecommitdiff
path: root/libs/kstd/gdb/__init__.py
diff options
context:
space:
mode:
authorFelix Morgner <felix.morgner@ost.ch>2026-09-04 20:25:14 +0200
committerFelix Morgner <felix.morgner@ost.ch>2026-09-04 20:25:14 +0200
commitf00223b5cc99a8f3f1b6a15658d8c854c177932a (patch)
tree4b90b707b4331c7956a098864da7ea1e5e657ad0 /libs/kstd/gdb/__init__.py
parenta5848c037e6e681d586312ddddddd200b9f7a5b0 (diff)
downloadkernel-f00223b5cc99a8f3f1b6a15658d8c854c177932a.tar.xz
kernel-f00223b5cc99a8f3f1b6a15658d8c854c177932a.zip
x86_64/cpu: handle #DF inside the arch code
A double fault is a very x86-64 specific type of exception and not recoverable in a generalized way. Thus we should handle it internally, with handling currently being triggering a panic, and not forward it to the architecture-independent kernel layer.
Diffstat (limited to 'libs/kstd/gdb/__init__.py')
0 files changed, 0 insertions, 0 deletions