author | Cameron McCormack <cam@mcc.id.au> |
Mon, 10 Feb 2014 08:50:48 +1100 | |
changeset 184971 | d10ea4b8dfae0c43d9b50a770d499e7a7a067f91 |
parent 184970 | a3cddd4f926bda81bebe64d1c495ac5457eb9142 |
child 184972 | 93f2c8487cf75b930cd940980f352cb1efc48243 |
push id | 3503 |
push user | raliiev@mozilla.com |
push date | Mon, 28 Apr 2014 18:51:11 +0000 |
treeherder | mozilla-beta@c95ac01e332e [default view] [failures only] |
perfherder | [talos] [build metrics] [platform microbench] (compared to previous push) |
bugs | 969941 |
milestone | 30.0a1 |
first release with | nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
|
last release without | nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
|
--- a/python/lldbutils/README.txt +++ b/python/lldbutils/README.txt @@ -120,17 +120,19 @@ In lldb terminology, type summaries are when using the "expression" command (or its familiar-to-gdb-users "p" alias), and synthetic children are fake member variables or array elements also added by custom rules. For objects that do have synthetic children defined for them, like nsTArray, the "expr -R -- EXPR" command can be used to show its actual member variables. -* nsAString, nsACString +* nsAString, nsACString, + nsFixedString, nsFixedCString, + nsAutoString, nsAutoCString Strings have a type summary that shows the actual string. (lldb) frame info frame #0: 0x000000010400cfea XUL`nsCSSParser::ParseProperty(this=0x00007fff5fbf5248, aPropID=eCSSProperty_margin_top, aPropValue=0x00007fff5fbf53f8, aSheetURI=0x0000000115ae8c00, aBaseURI=0x0000000115ae8c00, aSheetPrincipal=0x000000010ff9e040, aDeclaration=0x00000001826fd580, aChanged=0x00007fff5fbf5247, aIsImportant=false, aIsSVGMode=false) + 74 at nsCSSParser.cpp:12851 (lldb) p aPropValue (const nsAString_internal) $16 = u"-25px"