Lines Matching refs:LLDB
7 LLDB has a data formatters subsystem that allows users to define custom display
10 Usually, when you type ``frame variable`` or run some expression LLDB will
25 as to how variables should be displayed. The LLDB type command allows you to do
107 printed, LLDB will first check if custom printing options have been associated
133 at the LLDB command line.
175 This is because by default LLDB cascades formats through typedef chains. In
210 and --skip-references (-r). These two options prevent LLDB from applying a
255 | ``default`` | | the default LLDB algorithm is …
375 processed by LLDB to generate the summary.
442 ``${*var`` tells LLDB to get the object that the expression paths leads to, and
509 Option --inline-children (-c) to type summary add tells LLDB not to look for a summary string, but …
569 To cope with the issue, LLDB supports native bitfield formatting in summary
572 unsigned variants), you can ask LLDB to only grab some bits out of the value
588 In this example, LLDB shows the internal representation of a float variable by
594 LLDB also allows to use a similar syntax to display array members inside a summary string. For inst…
623 …ly this summary string to every element of the array. Here, we are asking LLDB to display .x for e…
634 You can also ask LLDB to only print a subset of the array range by using the
650 In general, LLDB needs the square brackets ``operator []`` in order to handle
661 This syntax works for char* as well as for char[] because LLDB can rely on the
664 LLDB has default summary strings for char* and char[] that use this special
681 LLDB to detect the end of the pointed data.
741 In order to write effective summary scripts, you need to know the LLDB public
742 API, which is the way Python code can access the LLDB object model. For further
743 details on the API you should look at the LLDB API reference documentation.
749 ``internal_dict`` is an internal support parameter used by LLDB and you should
795 LLDB will emit a warning if it is unable to find the function you passed, but
822 expression matching is slower than normal name matching, LLDB will first try to
826 One of the ways LLDB uses this feature internally, is to match the names of STL
830 The regular expression language used by LLDB is the POSIX extended language, as
845 command, supports a --summary option that tells LLDB to use the named summary
870 order for LLDB to do so, appropriate debugging information must be available.
931 …this call should return a new LLDB SBValue object representing the child at the index given as arg…
933 …te the internal state of this Python object whenever the state of the variables in LLDB changes.[1]
941 silently by LLDB and should be handled appropriately by the formatter itself.
942 Being more specific, in case of exceptions, LLDB might assume that the given
969 including it in the range of children displayed by LLDB. For example,
991 at examples/synthetic in the LLDB trunk. Please, be aware that the code in
996 The design pattern consistently used in synthetic providers shipping with LLDB
999 synthetic children provider is written, one must load it into LLDB before it
1000 can be used. Currently, one can use the LLDB script command to type Python code
1009 children provider in LLDB:
1021 LLDB has synthetic children providers for a core subset of STL classes, both in
1028 This symbol tells LLDB to refer expression paths to the synthetic children
1042 It's important to mention that LLDB invokes the synthetic child provider before
1049 a variable that has a synthetic child provider, notice that LLDB hides the
1060 In some cases, if LLDB is unable to use the real object to get a child
1150 default, LLDB will not show you the real type of the object. it can actually
1165 If you specify a value of either no-run-target or run-target, LLDB will detect
1176 Because LLDB uses a detection algorithm that does not need to invoke any
1180 into LLDB. It was initially implemented through Python (the code is still
1183 compiled into the LLDB core).
1188 Categories are a way to group related formatters. For instance, LLDB itself
1193 By default, several categories are created in LLDB:
1215 LLDB uses that order when looking for formatters. Therefore, when you enable a
1233 older versions of LLDB which had built-in formatters for these types. Because
1253 However, in this case LLDB warns you that enabling an empty category has no
1265 that LLDB starts looking in each enabled category, according to the order in
1266 which they were enabled (latest enabled first). In each category, LLDB does the
1278 - If this object's type is a typedef, go through typedef hierarchy (LLDB might
1282 the correct debugging information for LLDB to cascade). If at any level of
1293 **Warning**: previous versions of LLDB defined cascading to mean not only going