Blame - www/python-reference.html - fp2-dev/platform/external/lldb

2012-01-24 02:40:42 +0000

[diff] [blame]

85

The embedded python interpreter can be accessed in a variety of ways from within LLDB. The

86

easiest way is to use the lldb command script with no arguments at the lldb command prompt:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

87

<code><pre><tt>(lldb) script

88

Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.

>>> 2+3

5

>>> hex(12345)

'0x3039'

>>>

</tt></pre></code>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

96

This drops you into the embedded python interpreter. When running under the script command,

97

lldb sets some convenience variables that give you quick access to the currently selected entities that characterize

98

the program and debugger state. In each case, if there is no currently selected entity of the appropriate

99

type, the variable's IsValid method will return false.

100

Note also, these variables hold the values

101

of the selected objects on entry to the embedded interpreter. They do not update as you use the LLDB

102

API's to change, for example, the currently selected stack frame or thread.

103

These are all global variables contained in the lldb python namespace :

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

104

105

<tr>

106

<td class="hed" width="20%">Variable</td>

107

108

<td class="hed" width="70%">Description</td>

</tr>

<tr>

lldb.debugger

</td>

lldb.SBDebugger

</td>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

119

Contains the debugger object whose script command was invoked.

120

The lldb.SBDebugger object owns the command interpreter

121

and all the targets in your debug session. There will always be a

122

Debugger in the embedded interpreter.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

</tr>

<tr>

lldb.target

</td>

lldb.SBTarget

</td>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

133

Contains the currently selected target - for instance the one made with the

134

file or selected by the target select <target-index> command.

135

The lldb.SBTarget manages one running process, and all the executable

136

and debug files for the process.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

</tr>

<tr>

lldb.process

</td>

lldb.SBProcess

</td>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

147

Contains the process of the currently selected target.

148

The lldb.SBProcess object manages the threads and allows access to

149

memory for the process.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

</tr>

<tr>

lldb.thread

</td>

lldb.SBThread

</td>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

160

Contains the currently selected thread.

161

The lldb.SBThread object manages the stack frames in that thread.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

162

A thread is always selected in the command interpreter when a target stops.

163

The thread select <thread-index> commmand can be used to change the

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

164

currently selected thread. So as long as you have a stopped process, there will be

165

some selected thread.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

</tr>

<tr>

lldb.frame

</td>

lldb.SBFrame

</td>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

176

Contains the currently selected stack frame.

177

The lldb.SBFrame object manage the stack locals and the register set for

178

that stack.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

179

A stack frame is always selected in the command interpreter when a target stops.

180

The frame select <frame-index> commmand can be used to change the

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

181

currently selected frame. So as long as you have a stopped process, there will

182

be some selected frame.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

</tr>

</table>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

187

Once in the embedded interpreter, these objects can be used. To get started, note that almost

188

all of the lldb Python objects are able to briefly describe themselves when you pass them

189

to the Python print function:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

190

<code><pre><tt>(lldb) script

191

Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.

192

>>> print lldb.debugger

193

Debugger (instance: "debugger_1", id: 1)

194

>>> print lldb.target

195

a.out

196

>>> print lldb.process

197

SBProcess: pid = 59289, state = stopped, threads = 1, executable = a.out

198

>>> print lldb.thread

199

SBThread: tid = 0x1f03

200

>>> print lldb.frame

201

frame #0: 0x0000000100000bb6 a.out main + 54 at main.c:16

</tt></pre></code>

</div>

</div>

<h1 class ="postheader">Running a Python script when a breakpoint gets hit</h1>

210

211

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

212

One very powerful use of the lldb Python API is to have a python script run when a breakpoint gets hit. Adding python

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

213

scripts to breakpoints provides a way to create complex breakpoint

214

conditions and also allows for smart logging and data gathering.

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

215

When your process hits a breakpoint to which you have attached some python code, the code is executed as the

216

body of a function which takes two arguments:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

217

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

218

<code><pre><tt>def breakpoint_function_wrapper(frame, bp_loc):

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

219

# Your code goes here

</tt></pre></code>

<tr>

<td class="hed" width="10%">Argument</td>

224

225

<td class="hed" width="80%">Description</td>

</tr>

<tr>

frame

</td>

lldb.SBFrame

</td>

The current stack frame where the breakpoint got hit.

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

237

The object will always be valid.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

238

This frame argument might not match the currently selected stack frame found in the lldb module global variable lldb.frame.

</td>

</tr>

<tr>

bp_loc

</td>

lldb.SBBreakpointLocation

247

</td>

248

249

The breakpoint location that just got hit. Breakpoints are represented by lldb.SBBreakpoint

250

objects. These breakpoint objects can have one or more locations. These locations

251

are represented by lldb.SBBreakpointLocation objects.

252

</td>

253

</tr>

254

</table>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

255

An example will show how simple it is to write some python code and attach it to a breakpoint.

256

The following example will allow you to track the order in which the functions in a given shared library

257

are first executed during one run of your program. This is a simple method to gather an order file which

258

can be used to optimize function placement within a binary for execution locality.

259

We do this by setting a regular expression breakpoint

260

that will match every function in the shared library. The regular expression '.' will match

261

any string that has at least one character in it, so we will use that.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

262

This will result in one lldb.SBBreakpoint object

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

263

that contains an lldb.SBBreakpointLocation object for each function. As the breakpoint gets

264

hit, we use a counter to track the order in which the function at this particular breakpoint location got hit.

265

Since our code is passed the location that was hit, we can get the name of the function from the location,

266

disable the location so we won't count this function again; then log some info and continue the process.

267

Note we also have to initialize our counter, which we do with the simple one-line version of the script

command.

Here is the code:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

271

<code><pre><tt>(lldb) breakpoint set --func-regex=. --shlib=libfoo.dylib

272

Breakpoint created: 1: regex = '.', module = libfoo.dylib, locations = 223

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

273

(lldb) script counter = 0

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

274

(lldb) breakpoint command add --script-type python 1

275

Enter your Python command(s). Type 'DONE' to end.

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

276

> # Increment our counter. Since we are in a function, this must be a global python variable

277

> global counter

278

> counter += 1

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

279

> # Get the name of the function

280

> name = frame.GetFunctionName()

281

> # Print the order and the function name

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

282

> print '[%i] %s' % (counter, name)

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

283

> # Disable the current breakpoint location so it doesn't get hit again

284

> bp_loc.SetEnabled(False)

285

> # How continue the process

286

> frame.GetThread().GetProcess().Continue()

287

> DONE

288

</tt></pre></code>

289

The breakpoint command add command above attaches a python script to breakpoint 1.

290

To remove the breakpoint command:

291

<code>(lldb) breakpoint command delete 1</code>

</div>

</div>

<h1 class ="postheader">Create a new LLDB command using a python function</h1>

296

297

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

298

Python functions can be used to create new LLDB command interpreter commands, which will work

299

like all the natively defined lldb commands. This provides a very flexible and easy way to extend LLDB to meet your

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

300

debugging requirements.

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

301

To write a python function that implements a new LDB command define the function to take four arguments as follows:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

302

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

303

<code><pre><tt>def command_function(debugger, command, result, internal_dict):

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

304

# Your code goes here

305

</tt></pre></code>

Enrico Granata

c0791aa

2012-05-02 21:00:41 +0000

[diff] [blame]

306

307

Optionally, you can also provide a Python docstring, and LLDB will use it when providing help for your command, as in:

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

308

<code><pre><tt>def command_function(debugger, command, result, internal_dict):

Enrico Granata

c0791aa

2012-05-02 21:00:41 +0000

[diff] [blame]

309

"""This command takes a lot of options and does many fancy things"""

310

# Your code goes here

311

</tt></pre></code>

312

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

313

314

<tr>

315

<td class="hed" width="10%">Argument</td>

316

317

<td class="hed" width="80%">Description</td>

</tr>

<tr>

debugger

</td>

lldb.SBDebugger

</td>

The current debugger object.

</td>

</tr>

<tr>

command

</td>

python string

</td>

A python string containing all arguments for your command. If you need to chop up the arguments

340

try using the shlex module's <code>shlex.split(command)</code> to properly extract the

arguments.

</td>

</tr>

<tr>

result

</td>

lldb.SBCommandReturnObject

350

</td>

351

352

A return object where you can indicate the success or failure of your command. You can also

353

provide information for the command result by printing data into it. You can also just print

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

354

data as you normally would in a python script and the output will show up; this is useful for

355

logging, but the real output for your command should go in the result object.

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

</tr>

<tr>

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

360

internal_dict

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

</td>

python dict object

</td>

The dictionary for the current embedded script session which contains all variables

and functions.

</td>

</tr>

</table>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

371

One other handy convenience when defining lldb command-line commands is the command

372

command script import which will import a module specified by file path - so you

373

don't have to change your PYTHONPATH for temporary scripts. It also has another convenience

374

that if your new script module has a function of the form:

375

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

376

<code><pre><tt>def __lldb_init_module(debugger, internal_dict):

Greg Clayton

261c974

2012-01-26 05:36:07 +0000

[diff] [blame]

377

# Command Initialization code goes here

378

</tt></pre></code>

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

379

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

380

where debugger and internal_dict are as above, that function will get run when the module is loaded

Greg Clayton

261c974

2012-01-26 05:36:07 +0000

[diff] [blame]

381

allowing you to add whatever commands you want into the current debugger. Note that

382

this function will only be run when using the LLDB comand command script import,

383

it will not get run if anyone imports your module from another module.

384

If you want to always run code when your module is loaded from LLDB

385

or when loaded via an import statement in python code

386

you can test the lldb.debugger object, since you imported the

387

<lldb> module at the top of the python ls.py module. This test

388

must be in code that isn't contained inside of any function or class,

389

just like the standard test for __main__ like all python modules

390

usally do. Sample code would look like:

391

392

<code><pre><tt>if __name__ == '__main__':

393

# Create a new debugger instance in your module if your module

394

# can be run from the command line. When we run a script from

395

# the command line, we won't have any debugger object in

396

# lldb.debugger, so we can just create it if it will be needed

397

lldb.debugger = lldb.SBDebugger.Create()

398

elif lldb.debugger:

399

# Module is being run inside the LLDB interpreter

400

lldb.debugger.HandleCommand('command script add -f ls.ls ls')

401

print 'The "ls" python command has been installed and is ready for use.'

402

</tt></pre></code>

403

Now we can create a module called ls.py in the file ~/ls.py that will implement a function that

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

404

can be used by LLDB's python command code:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

405

406

<code><pre><tt>#!/usr/bin/python

import lldb

import commands

import optparse

import shlex

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

413

def ls(debugger, command, result, internal_dict):

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

414

result.PutCString(commands.getoutput('/bin/ls %s' % command))

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

415

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

416

# And the initialization code to add your commands

Enrico Granata

2012-08-08 02:06:30 +0000

[diff] [blame]

417

def __lldb_init_module(debugger, internal_dict):

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

418

debugger.HandleCommand('command script add -f ls.ls ls')

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

419

print 'The "ls" python command has been installed and is ready for use.'

420

</tt></pre></code>

421

Now we can load the module into LLDB and use it

422

<code><pre><tt>% lldb

Greg Clayton

261c974

2012-01-26 05:36:07 +0000

[diff] [blame]

423

(lldb) command script import ~/ls.py

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

424

The "ls" python command has been installed and is ready for use.

425

(lldb) ls -l /tmp/

426

total 365848

427

-rw-r--r--@ 1 someuser wheel 6148 Jan 19 17:27 .DS_Store

428

-rw------- 1 someuser wheel 7331 Jan 19 15:37 crash.log

429

</tt></pre></code>

430

A template has been created in the source repository that can help you to create

431

lldb command quickly:

432

<a href="http://llvm.org/svn/llvm-project/lldb/trunk/examples/python/cmdtemplate.py">cmdtemplate.py</a>

Enrico Granata

74566c9

2012-08-24 21:20:14 +0000

[diff] [blame^]

433

434

A commonly required facility is being able to create a command that does some token substitution, and then runs a different debugger command

435

(usually, it po'es the result of an expression evaluated on its argument). For instance, given the following program:

436

437

#import <Foundation/Foundation.h>

438

NSString*

439

ModifyString(NSString* src)

440

{

441

return [src stringByAppendingString:@"foobar"];

}

int main()

{

NSString* aString = @"Hello world";

447

NSString* anotherString = @"Let's be friends";

return 1;

}

</tt></pre></code>

you may want a pofoo X command, that equates po [ModifyString(X) capitalizedString].

452

The following debugger interaction shows how to achieve that goal:

453

454

(lldb) script

455

Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.

456

>>> def pofoo_funct(debugger, command, result, internal_dict):

457

... cmd = "po [ModifyString(" + command + ") capitalizedString]"

458

... lldb.debugger.HandleCommand(cmd)

459

...

460

>>> ^D

461

(lldb) command script add pofoo -f pofoo_funct

462

(lldb) pofoo aString

463

$1 = 0x000000010010aa00 Hello Worldfoobar

464

(lldb) pofoo anotherString

465

$2 = 0x000000010010aba0 Let's Be Friendsfoobar</tt></pre></code>

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

466

</div>

467

468

<h1 class ="postheader">Using the lldb.py module in python</h1>

469

470

471

LLDB has all of its core code build into a shared library which gets

472

used by the lldb command line application. On Mac OS X this

473

shared library is a framework: LLDB.framework and on other

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

474

unix variants the program is a shared library: lldb.so. LLDB also

475

provides an lldb.py module that contains the bindings from LLDB into Python.

476

To use the

477

LLDB.framework to create your own stand-alone python programs, you will

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

478

need to tell python where to look in order to find this module. This

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

479

is done by setting the PYTHONPATH environment variable, adding

480

a path to the directory that contains the lldb.py python module. On

481

Mac OS X, this is contained inside the LLDB.framework, so you would do:

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

482

483

For csh and tcsh:

484

<code>% setenv PYTHONPATH /Developer/Library/PrivateFrameworks/LLDB.framework/Resources/Python</code>

485

For sh and bash:

486

<code>% export PYTHONPATH=/Developer/Library/PrivateFrameworks/LLDB.framework/Resources/Python</code>

487

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

488

Alternately, you can append the LLDB Python directory to the sys.path list directly in

489

your Python code before importing the lldb module.

490

Greg Clayton

2012-01-22 02:55:08 +0000

[diff] [blame]

491

492

Now your python scripts are ready to import the lldb module. Below is a

493

python script that will launch a program from the current working directory

494

called "a.out", set a breakpoint at "main", and then run and hit the breakpoint,

495

and print the process, thread and frame objects if the process stopped:

496

497

498

<code><pre><tt>#!/usr/bin/python

import lldb

# Set the path to the executable to debug

503

exe = "./a.out"

504

505

# Create a new debugger instance

506

debugger = lldb.SBDebugger.Create()

507

508

# When we step or continue, don't return from the function until the process

Jim Ingham

2012-01-24 02:40:42 +0000

[diff] [blame]

509

# stops. Otherwise we would have to handle the process events ourselves which, while doable is

510

#a little tricky. We do this by setting the async mode to false.

Greg Clayton