Changes between Version 3 and Version 4 of DebuggingGhcCrashes


Ignore:
Timestamp:
Mar 31, 2006 11:04:39 AM (9 years ago)
Author:
simonmar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DebuggingGhcCrashes

    v3 v4  
    5757 * Look at the fragment of code that crashed: {{{disassemble}}}.  It
    5858   should be pretty small (code blocks in GHC-generated code usually
    59    are).  Look at the instruction that caused the crash (the address
    60    is given in the {{{where}}} output earlier).  If you can tell what
     59   are).  Look at the instruction that caused the crash - the address
     60   is given in the {{{where}}} output earlier.  If you can tell what
    6161   the problem is right there, then great.
    6262
     
    6666 * Make the crash happen repeatably, if possible.  That means after
    6767   the exact same number of garbage collections and context switches
    68    each time.
    69 
    70    Use {{{+RTS -C0}}} to turn off timer-based context switches.  If
     68   each time. Use {{{+RTS -C0}}} to turn off timer-based context switches.  If
    7169   you're debugging heap profiling, add {{{-i0}}} too.
    7270
     
    167165looking at heap & stack objects in a running program.
    168166
    169 You can display memory in gdb with something like {{{x/8a}}} to
     167You can display memory in gdb with something like {{{x/4a}}} to
    170168display 4 words of memory, or using our [attachment:".gdbinit" gdb macros] you get slighty
    171169nicer output: