Changes between Version 5 and Version 6 of DebugTips


Ignore:
Timestamp:
Oct 21, 2013 7:13:37 PM (4 years ago)
Author:
MichaelRay
Comment:

debuggable ?
for long lines

Legend:

Unmodified
Added
Removed
Modified
  • DebugTips

    v5 v6  
    1111If it isn't, you'll have to rebuild mutt with debugging support:
    1212
    13 == Building a debuggable mutt ==
     13== Build-enable debugging in mutt ==
    1414
    1515 * pass the `--enable-debug` flag to `configure` along with any other flags you need.
     
    2525 5. everything, even very confidential information like passwords
    2626
    27 For most purposes, level 2 provides the right amount of detail for a bug report. It may also include some confidential information (email addresses, server URLs), so you should read it over before you send it to anyone. Feel free to sanitize it -- we'll ask for further information if necessary.
     27For most purposes, level 2 provides the right amount of detail for a bug report.[[br]]
     28It may also include some confidential information (email addresses, server URLs), so you should read it over before you send it to anyone.[[br]]
     29Feel free to sanitize it -- we'll ask for further information if necessary.
    2830
    2931== Analyzing a crash ==
     
    3739=== If you don't ===
    3840
    39 One common reason for not getting a core dump when mutt crashes is `ulimit`. If running `ulimit -c` returns `0`, that means core dumps are disabled in your login session. Try executing `ulimit -c unlimited`, then running mutt again.
     41One common reason for not getting a core dump when mutt crashes is `ulimit`. [[br]]
     42If running `ulimit -c` returns `0`, that means core dumps are disabled in your login session. Try executing `ulimit -c unlimited`, then running mutt again.
    4043
    4144If you still don't have a core dump, you can always run mutt inside of gdb, then generate the backtrace when it crashes: