Lines Matching refs:be

26 lldb can be used for kernel debugging the same way as gdb. The simplest way is to start lldb with k…
31 Now lldb will be ready to connect over kdp-remote '\<hostname:port>' or 'gdb-remote \<hostname:port…
52 …sic lldb commands like print, bt, expr etc. The xnu debug macros will also be loaded automatically…
64 These could be very handy in printing important information from structures easily.
88 …The command interface provides some common features (which can be invoked after passing '--' on cm…
127 … command please type 'help <command name>' and the documentation for the command will be displayed.
156 … command interface and core utility function so that any function/code can be called as a simple u…
171       - remember that the ideal type of object to be passed around is core.value
172       - Anything you 'print' will be relayed to lldb terminal output.
174 …d any custom options they would be in cmd_options dict. the format is `{'-<optionflag>':'<value>'}…
178 …mmenting your code. This is important because single "#" based strings may be mistakenly considere…
207 The lldb debugger provides ways for user to customize how a particular type of object be described …
224 …rface for building summaries for complex objects and data. If you find that a struct or list can be
232 … of `GetSomeTypeSummary(valobj)`. It is highly recommended that the naming be consistent to `Get.*…
237      [ remember that the ideal type of object to be passed around is core.value ]
239 …5. return a string that would be printed by the caller. When lldb makes a call back it expects a s…
240      directly out to console. [ debug info or logs output is okay to be printed anywhere :) ]
295 …accepts pointers (eg showtaskstacks etc). In order to have your expression be evaluated before pas…
316 …* any python string can be invoked to "".format() and hence makes it very easy to play with formats
345                 a - int, value to be added. can be 0
346                 b - int/float, value to be added.
353 …* A Class or Function should always start with CAPITAL letter and be CamelCase. If a function is f…
355  * Function params should always be lower_case and be word separated with '_'
357  * A local variable inside a function should be lower_case and separated with '_'
363 …tching `Get(.*?)Summary()` is always supposed to return a string which can be printed on stdout or…
413 …the command code will try to read and show some results. It may still be junk or plain erronous. P…
417 …debugging is particularly tricky. Many parts of memory may not be readable. There could be failure…
422     and a exception to be thrown.