.lldbinit
author Ryan VanderMeulen <ryanvm@gmail.com>
Wed, 09 Aug 2017 21:31:30 -0400
changeset 373751 0cd4ced6047668902e3dbb2373c2dab0e99dd04f
parent 362829 ff64a7889c1fac56d48205fc2fad4eb5aa481a73
child 385053 67a8e12324569dd730347187e2ffccae486c758b
permissions -rw-r--r--
Backed out 7 changesets (bug 1387862) for yaml linting failures. Backed out changeset 63f87f6db7d6 (bug 1387862) Backed out changeset a85b7e7d9f24 (bug 1387862) Backed out changeset 3713ea9672e8 (bug 1387862) Backed out changeset 22c1094e387f (bug 1387862) Backed out changeset e0bfb35b0eec (bug 1387862) Backed out changeset 5bb5dc7655ec (bug 1387862) Backed out changeset cc4c01794114 (bug 1387862)

# .lldbinit file for debugging Mozilla

# -----------------------------------------------------------------------------
# For documentation on all of the commands and type summaries defined here and
# in the accompanying Python scripts, see third_party/python/lldbutils/README.txt.
# -----------------------------------------------------------------------------

# Import the module that defines complex Gecko debugging commands.  This assumes
# you are either running lldb from the top level source directory, the objdir,
# or the dist/bin directory.  (.lldbinit files in the objdir and dist/bin set
# topsrcdir appropriately.)
script topsrcdir = topsrcdir if locals().has_key("topsrcdir") else os.getcwd(); sys.path.append(os.path.join(topsrcdir, "third_party/python/lldbutils")); import lldbutils; lldbutils.init()

# Mozilla's use of UNIFIED_SOURCES to include multiple source files into a
# single compiled file breaks lldb breakpoint setting. This works around that.
# See http://lldb.llvm.org/troubleshooting.html for more info.
settings set target.inline-breakpoint-strategy always

# Show the dynamic type of an object when using "expr".  This, for example,
# will show a variable declared as "nsIFrame *" that points to an nsBlockFrame
# object as being of type "nsBlockFrame *" rather than "nsIFrame *".
settings set target.prefer-dynamic-value run-target

# Show the string value in atoms.
type summary add nsIAtom --summary-string "${var.mString}"

# Show the value of text nodes.
type summary add nsTextNode --summary-string "${var.mText}"

# Dump the current JS stack.
command alias js expr DumpJSStack()