Changes between Initial Version and Version 1 of doc/tracingCrash

Timestamp:

08/27/09 12:03:06 (15 years ago)

Author:

iNode

Comment:

initial commit

doc/tracingCrash

@@ +1 @@
+So, you get '''Segmentatiоn fault''' message, what should you do with this?
+
+You should report about crash to developers. Please provide detailed description.
+
+== How to ==
+1. You should build '''mc''' with maximum debug info enabled.
+
+{{{
+$ ./configure <common-options>
+$ make CFLAGS=-ggdb3 # here it is!
+$ make install
+}}}
+
+2. Allow to create core dumps (you should run '''mc''' in the same session where you do it)
+{{{
+$ ulimit -c unlimited
+$ mc
+}}}
+
+3. So, crash it! And get a maximum info from '''core''' file of '''mc''' (in directory where '''mc''' crash):
+{{{
+$ gdb --quiet /usr/bin/mc core
+...
+(gdb) bt
+<usefull-output-1>
+(gdb) bt full
+<usefull-output-2>
+}}}
+4. Copy '''usefull-output-1''' and '''usefull-output-2''' and send report to [wiki:defectReports tracker] (or in mc-devel at gnome.org mail-list or in developers jabber conference: mc-dev@conference.jabber.org). Please don't forget also describe your build ('''./configure''') options and how to reproduce crash.
+
+[http://www.midnight-commander.org/browser/doc/FAQ] <- FAQ 10.3 (the similar article in FAQ)