Diff for "Debugging/CoreDumps"

Differences between revisions 3 and 4

A quick sketch of how to read core files produced from production machines by webops.

Have core dump files moved to osageorange
Ensure you have access to osageorange
You'll need to ping webops on #launchpad-ops to get access; you cannot ssh from devpad to osageorange.
Get pygdb (lp:pygdb) in your $HOME on osageorange
ssh to orageorange, and do
schroot -c lucid-cat-amd64
This puts you in a chroot with the same packages installed as on production.
Then cd into pygdb dir and do something like:
python backtrace.py -c $PATH_TO_FILE/core.XXX > ~/core.XXX-out.txt
Read output and profit!

-  ⇤ ← Revision 3 as of 2012-02-01 20:19:09 → 
  Size: 345
  Editor: deryck
  Comment:
+   ← Revision 4 as of 2012-02-07 15:40:41 → ⇥
  Size: 650
  Editor: deryck
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-Working on draft of core dump reading how to...
+== A quick sketch of how to read core files produced from production machines by webops. ==
 Line 4:
-. Ensure you have access to osageorange
 3. schroot -c lucid-cat-amd64<<BR>>This puts you in a chroot with the same packages installed as on production.

(Steps 1 and 2 require webops assistance.  There is no ssh from devpad to osageorange.
+. Ensure you have access to osageorange<<BR>>You'll need to ping webops on #launchpad-ops to get access; you cannot ssh from devpad to osageorange.
 3. Get pygdb (lp:pygdb) in your $HOME on osageorange
 4. ssh to orageorange, and do<<BR>>`schroot -c lucid-cat-amd64`<<BR>>This puts you in a chroot with the same packages installed as on production.
 5. Then cd into pygdb dir and do something like:<<BR>>`python backtrace.py -c $PATH_TO_FILE/core.XXX > ~/core.XXX-out.txt`
 6. Read output and profit!