Diff for "Debugging/CoreDumps"

Not logged in - Log In / Register
Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2012-02-07 15:40:41 →
Size: 650
Editor: deryck
Comment:
← Revision 5 as of 2019-08-22 11:38:51 → ⇥
Size: 654
Editor: cjwatson
Comment: webops → IS
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== A quick sketch of how to read core files produced from production machines by webops. == == A quick sketch of how to read core files produced from production machines by IS. ==
Line 4: Line 4:
 2. 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.  2. Ensure you have access to osageorange<<BR>>You'll need to ping a member of IS on #launchpad-ops to get access; you cannot ssh from devpad to osageorange.

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

  1. Have core dump files moved to osageorange

  2. Ensure you have access to osageorange
    You'll need to ping a member of IS 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
    schroot -c lucid-cat-amd64
    This puts you in a chroot with the same packages installed as on production.

  5. Then cd into pygdb dir and do something like:
    python backtrace.py -c $PATH_TO_FILE/core.XXX > ~/core.XXX-out.txt

  6. Read output and profit!

Debugging/CoreDumps (last edited 2019-08-22 11:38:51 by cjwatson)