https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394

--- Comment #14 from Mark Johnston <ma...@freebsd.org> ---
(In reply to Gregory Neil Shapiro from comment #10)
So, if you're building a kernel from releng/14.0, GENERIC doesn't have
debugging options enabled.  DEBUG+=-g merely instructs the compiler to include
debug symbols in the output, which helps debuggers but doesn't enable
assertions, invariants checking, etc..

We don't include a debug kernel config on releng branches (this is a problem to
be fixed).  You can add the following lines (taken from GENERIC on main) to
enable more checking which will hopefully catch a problem before the double
fault occurs:

# For full debugger support use (turn off in stable branch):                    
options         BUF_TRACKING            # Track buffer history                  
options         DDB                     # Support DDB.                          
options         FULL_BUF_TRACKING       # Track more buffer history             
options         GDB                     # Support remote GDB.                   
options         DEADLKRES               # Enable the deadlock resolver          
options         INVARIANTS              # Enable calls of extra sanity checking 
options         INVARIANT_SUPPORT       # Extra sanity checks of internal
structures, required by INVARIANTS                                              
options         QUEUE_MACRO_DEBUG_TRASH # Trash queue(2) internal pointers on
invalidation                                                                    
options         WITNESS                 # Enable checks to detect deadlocks and
cycles                                                                          
options         WITNESS_SKIPSPIN        # Don't run witness on spinlocks for
speed                                                                           
options         MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones              
options         VERBOSE_SYSINIT=0       # Support debug.verbose_sysinit, off by
default

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Reply via email to