Changes between Version 4 and Version 5 of MacBacktrace

Timestamp:

Mar 25, 2008, 5:55:32 PM (17 years ago)

Author:

Nicolas

Comment:

More monospaced blocks

MacBacktrace

@@ -22 +22 @@
 The BOINC Manager's executable is inside its bundle.  
 You can replace the 32-bit Intel manager on the command line thus:
-
-   sudo cp [path]/BOINCManager_i386 /Applications/BOINCManager.app/Contents/MacOS/BOINCManager
-
+{{{
+sudo cp [path]/BOINCManager_i386 /Applications/BOINCManager.app/Contents/MacOS/BOINCManager
+}}}
 You should then confirm that the ownership and permissions have not changed:
+{{{
 ls -al /Applications/BOINCManager.app/Contents/MacOS
+}}}
 and you should see something like this:
+{{{
 -r-xr-sr-x  1 boinc_master  boinc_master  9197816 Mar 12 03:04 BOINCManager
+}}}
 
 Note that you must rename the unstripped executable to have the same file name as the original.
@@ -40 +44 @@
 This will work for project applications as well as the BOINC Manager and Client, but not for separate .dSYM files:
 
-For example, to find a symbol in BOINC Manager version 5.10.45, at the command line in the Terminal application, first enter: 
-   atos -o [path]/boinc_5.10.45_macOSX_SymbolTables/SymbolTables/BOINCManager_i386
+For example, to find a symbol in BOINC Manager version 5.10.45, at the command line in the Terminal application, first enter:
+{{{
+atos -o [path]/boinc_5.10.45_macOSX_SymbolTables/SymbolTables/BOINCManager_i386
+}}}
 then enter any number of hex values separated by spaces or carriage returns.  For example, entering the following:
-   0x0009dc57 0x0009de45 0x000151f1 0x0007210a
+{{{
+0x0009dc57 0x0009de45 0x000151f1 0x0007210a
+}}}
 will give the following output:
-   QCRGetBacktraceAtIndex (in BOINCManager_i386) (QCrashReport.c:623)
-   QCRPrintBacktraces (in BOINCManager_i386) (QCrashReport.c:756)
-   boinc_catch_signal (in BOINCManager_i386) (diagnostics.C:554)
-   CProgressBar::UpdateValue(double) (in BOINCManager_i386) (sg_ProgressBar.cpp:104)
+{{{
+QCRGetBacktraceAtIndex (in BOINCManager_i386) (QCrashReport.c:623)
+QCRPrintBacktraces (in BOINCManager_i386) (QCrashReport.c:756)
+boinc_catch_signal (in BOINCManager_i386) (diagnostics.C:554)
+CProgressBar::UpdateValue(double) (in BOINCManager_i386) (sg_ProgressBar.cpp:104)
+}}}
 
 == Use the GDB debugger to convert hex addresses to symbols == #gdb
@@ -55 +65 @@
 
 If the symbols are in the same file as the executable, or if the separate .dSYM file is in the same directory as the executable, first enter the following on the command line in the Terminal application:
-   gdb [path to executable file]
+{{{
+gdb [path to executable file]
+}}}
 If the executable file is not in the same directory as the .dSYM file, do this instead:
-   gdb
-   symbol [path to .dSYM file]
+{{{
+gdb
+symbol [path to .dSYM file]
+}}}
 
 Then, for each hex address of the form 0x12345678, enter the following:
-   info line *0x12345678
+{{{
+info line *0x12345678
+}}}
 Be sure to include the asterisk!