Changes between Initial Version and Version 1 of Ticket #10198, comment 5


Ignore:
Timestamp:
Nov 22, 2013, 2:24:48 PM (6 years ago)
Author:
isis
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10198, comment 5

    initial v1  
    119119
    120120 1) Start firefox with
    121       `./App/Firefox/firefox -no-remote -profile ./Data/profile -g` (for TBB-2.4)
    122    or
    123       `./Browser/firefox -no-remote -profile Data/Browser/profile.default -g`.
     121      `./App/Firefox/firefox -no-remote -profile ./Data/profile -g`
     122   (for TBB-2.4) or
     123      `./Browser/firefox -no-remote -profile Data/Browser/profile.default -g`
     124   (for TBB-3.0).
    124125
    125  2) At the gdb prompt (gdb), type `run --safe-mode`.
     126 2) At the gdb prompt (gdb), type:
     127      `run --safe-mode`.
    126128
    127  3) To get a stacktrace from a gdb shell, do: `thread apply all bt full`.
     129 3) To get a stacktrace from a gdb shell, do:
     130      `thread apply all bt full`.
    128131
    129132 4) To get a stacktrace from a coredump file (e.g. 'core.1234'), do:
    130133      `gdb <name-of-program> <core-filename>`
    131     then the command from step 3. Note that some distros disable coredumps by default in /etc/profile, to enable it temporarily in a shell do: `ulimit -c unlimited`.
     134    then the command from step 3. Note that some distros disable coredumps by default in /etc/profile, to enable it temporarily in a shell do:
     135      `ulimit -c unlimited`.
    132136
    133137=== The easiest thing to do ===
    134138
    135 Rather than go to all the work of reading assembler backtraces, or recompiling TBB, (equally difficult tasks, the latter of which would soon be undone, as soon as a stable TBB-3.0 is released and we deprecate the 2.4 series), you could try using [https://archive.torproject.org/tor-package-archive/torbrowser/ one of the new TBB-3.0 builds]. I believe that support for detached debug symbols was first enabled in TBB-3.0.2a (see #10148). If you were to get a copy of the new [https://archive.torproject.org/tor-package-archive/torbrowser/3.0rc1 TBB-3.0 release candidate bundle], in that directory there should also be a `tor-browser-linux64-debug.tar.gz` file. You'd want to untarball that `debug.tar.gz` archive in the top level of its corresponding TBB-3.0 directory. (In the example above, where I did `ls`, you can see the `Debug/` directory - that comes from untarballing the `debug.tar.gz`.) Then load the TBB firefox into gdb, as above, and then (I believe) the gdb command you want is:
     139Rather than go to all the work of reading assembler backtraces, or recompiling TBB, (equally difficult tasks, the latter of which would soon be undone, as soon as a stable TBB-3.0 is released and we deprecate the 2.4 series), you could try using [https://archive.torproject.org/tor-package-archive/torbrowser/ one of the new TBB-3.0 builds]. I believe that support for detached debug symbols was first enabled in TBB-3.0.2a (see #10126). If you were to get a copy of the new [https://archive.torproject.org/tor-package-archive/torbrowser/3.0rc1 TBB-3.0 release candidate bundle], in that directory there should also be a `tor-browser-linux64-debug.tar.gz` file. You'd want to untarball that `debug.tar.gz` archive in the top level of its corresponding TBB-3.0 directory. (In the example above, where I did `ls`, you can see the `Debug/` directory - that comes from untarballing the `debug.tar.gz`.) Then load the TBB firefox into gdb, as above, and then (I believe) the gdb command you want is:
    136140
    137141{{{