Home
last modified time | relevance | path

Searched refs:agent (Results 1 – 25 of 33) sorted by relevance

12

/art/test/909-attach-agent/
Drun18 agent=libtiagentd.so
20 agent=libtiagent.so
50 agent=${test_native_lib_path}/${agent}
64 --args agent:${agent}=909-attach-agent
70 --args agent:${agent}=909-attach-agent
74 --args agent:${agent}=909-attach-agent \
79 --args agent:${agent}=909-attach-agent \
Dexpected.txt3 Attached Agent for test 909-attach-agent
5 Attached Agent for test 909-attach-agent
10 Attached Agent for test 909-attach-agent
12 Attached Agent for test 909-attach-agent
17 Attached Agent for test 909-attach-agent
20 Attached Agent for test 909-attach-agent
26 Can't attach agent, process is not debuggable.
27 Can't attach agent, process is not debuggable.
/art/tools/jvmti-agents/titrace/
DREADME.md14 * `-Xplugin` and `-agentpath` need to be used, otherwise libtitrace agent will fail during init.
22 #### Enable permissions for attaching an agent
32 If this step is skipped, attaching the agent will not succeed.
33 #### Deploy agent to device
34 The agent must be located in an app-accessible directory.
42 Copy the agent into an app-accessible directory, and make the file owned by the app.
44 #### Attach agent to application
46 ##### Option 1: Attach the agent before any app code runs.
47 > `adb shell am start --attach-agent /data/data/com.littleinc.orm_benchmark/files/libtitrace.so com…
53 ##### Option 2: Attach the agent to an already-running app.
[all …]
/art/test/909-attach-agent/src-art/
DMain.java30 String agent = null; in main() local
35 agent = a.substring(6); in main()
40 if (agent == null) { in main()
46 VMDebug.attachAgent(agent); in main()
66 String agent = a.substring(6).replace(agentName, newAgentName); in attachWithClassLoader() local
71 VMDebug.attachAgent(agent, cl); in attachWithClassLoader()
/art/tools/jvmti-agents/simple-force-redefine/
DREADME.md3 ForceRedefine is a JVMTI agent designed for testing how redefiniton affects running processes. It
24 > `adb shell am attach-agent $(adb shell pidof some.deubggable.app) /data/local/tmp/libforcerede…
26 Since the agent has no static state it can be attached multiple times to the same process.
28 > `adb shell am attach-agent $(adb shell pidof some.deubggable.app) /data/local/tmp/libforcerede…
29 > `adb shell am attach-agent $(adb shell pidof some.deubggable.app) /data/local/tmp/libforcerede…
30 > `adb shell am attach-agent $(adb shell pidof some.deubggable.app) /data/local/tmp/libforcerede…
32 One can also use fifos to send classes interactively to the process. (TODO: Have the agent
/art/tools/jvmti-agents/jit-load/
DREADME.md3 Jitload is an art-specific agent allowing one to count the number of classes
15 * `-Xplugin` and `-agentpath` need to be used, otherwise libtitrace agent will fail during init.
16 * If using `libartd.so`, make sure to use the debug version of jvmti and agent.
17 * Pass the '=fatal' option to the agent to cause it to abort if any classes are
22 * To use with run-test or testrunner.py use the --with-agent argument.
24 > `./test/run-test --host --with-agent libtitraced.so=fatal 001-HelloWorld`
/art/tools/jvmti-agents/chain-agents/
DREADME.md3 The chainagents agent is a JVMTI agent that chain loads other agents from a file found at a
5 in order to implement more complicated agent-loading rules.
23 * `-Xplugin` and `-agentpath` need to be used, otherwise libtitrace agent will fail during init.
28 The chain-agents file is a list of agent files and arguments to load in the same format as the
/art/tools/jvmti-agents/wrapagentproperties/
DREADME.md3 wrapagentproperties is a JVMTI agent that lets one change the returned values of
15 …D_HOST_OUT/lib64/libwrapagentproperties.so=/path/to/prop.file,/path/to/agent=agent-args -cp tmp/ja…
17 * `-Xplugin` and `-agentpath` need to be used, otherwise libtitrace agent will fail during init.
/art/runtime/ti/
Dagent.cc78 std::unique_ptr<Agent> agent = DoDlOpen(env, class_loader, error, error_msg); in DoLoadHelper() local
79 if (agent == nullptr) { in DoLoadHelper()
83 AgentOnLoadFunction callback = attaching ? agent->onattach_ : agent->onload_; in DoLoadHelper()
106 return agent; in DoLoadHelper()
149 std::unique_ptr<Agent> agent(new Agent(name_, dlopen_handle)); in DoDlOpen() local
150 agent->PopulateFunctions(); in DoDlOpen()
152 return agent; in DoDlOpen()
/art/tools/jvmti-agents/enable-vlog/
DREADME.md3 enablevlog is a JVMTI agent designed for changing the VLOG options of a
18 The agent is loaded using -agentpath like normal. It takes arguments in the
28 At the time of writing, the following events may be listened for with this agent
86 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
93 > `adb shell am start-activity --attach-agent /data/local/tmp/libenablevlog.so=class,jit some.de…
/art/tools/jvmti-agents/breakpoint-logger/
DREADME.md3 breakpointlogger is a JVMTI agent that lets one set breakpoints that are logged
15 The agent is loaded using -agentpath like normal. It takes arguments in the
26 * Unlike with most normal debuggers the agent will load the class immediately to
37 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
46 …% ./test/run-test --host --dev --with-agent 'libbreakpointlogger.so=LMain;->main([Ljava/lang/Strin…
51 …% ./test/run-test --jvm --dev --with-agent 'libbreakpointlogger.so=LMain;->main([Ljava/lang/String…
/art/tools/jvmti-agents/ti-fast/
DREADME.md3 tifast is a JVMTI agent designed for profiling the performance impact listening
18 The agent is loaded using -agentpath like normal. It takes arguments in the
41 The following events may be listened for with this agent
95 All other events cannot be listened for by this agent. Most of these missing
102 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
109 > `adb shell am start-activity --attach-agent /data/local/tmp/libtifast.so=MonitorWait,ClassPrep…
/art/tools/jvmti-agents/dump-jvmti-state/
DREADME.md3 dumpjvmti is a JVMTI agent designed for helping debug the working of the openjdkjvmti plugin. It
18 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
25 > `adb shell am start-activity --attach-agent /data/local/tmp/libdumpjvmti.so some.debuggable.ap…
/art/tools/jvmti-agents/list-extensions/
DREADME.md3 listextensions is a jvmti agent that will print the details of all available jvmti extension
37 …agent or other clients can use. The agent is given the 'type' of the ddms chunk and a 'data_size' …
46 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
53 > `adb shell am start-activity --attach-agent /data/local/tmp/liblistextensions.so some.debuggab…
/art/tools/jvmti-agents/field-null-percent/
DREADME.md3 fieldnull is a JVMTI agent designed for testing for a given field the number of
17 The agent is loaded using -agentpath like normal. It takes arguments in the
24 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
31 > `adb shell am start-activity --attach-agent '/data/local/tmp/libfieldnulls.so=Ljava/lang/Class…
/art/tools/jvmti-agents/field-counts/
DREADME.md3 fieldcount is a JVMTI agent designed to investigate the types being held by specific fields and
6 Note that just by using the agent some fields might be written (for example fields related to
18 The agent is loaded using -agentpath like normal. It takes arguments in the
27 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
35 adb shell am start-activity --attach-agent '/data/local/tmp/libfieldcounts.so=Ljava/lang/Class;.ext…
/art/test/987-agent-bind/
Dinfo.txt1 Tests that native methods are bound from agent libs.
DAndroid.bp3 name: "art-run-test-987-agent-bind",
/art/test/etc/
Drun-test-jar598 for agent in "${WITH_AGENT[@]}"; do
599 FLAGS="${FLAGS} -agentpath:${agent}"
623 agent=libtiagentd.so
626 agent=libtiagent.so
632 FLAGS="${FLAGS} -agentpath:${ANDROID_HOST_OUT}/nativetest64/${agent}=${TEST_NAME},jvm"
635 FLAGS="${FLAGS} -agentpath:${agent}=${TEST_NAME},art"
640 FLAGS="${FLAGS} -agentpath:/data/${TEST_DIRECTORY}/art/${ISA}/${agent}=${TEST_NAME},art"
646 agent=libtistressd.so
648 agent=libtistress.so
670 FLAGS="${FLAGS} -agentpath:${ANDROID_HOST_OUT}/nativetest64/${agent}=${agent_args}"
[all …]
/art/test/931-agent-thread/
DAndroid.bp3 name: "art-run-test-931-agent-thread",
/art/test/901-hello-ti-agent/
DAndroid.bp3 name: "art-run-test-901-hello-ti-agent",
/art/test/1909-per-agent-tls/
DAndroid.bp3 name: "art-run-test-1909-per-agent-tls",
/art/tools/jvmti-agents/ti-alloc-sample/
DREADME.md3 tiallocsample is a JVMTI agent designed to track the call stacks of allocations
17 The agent is loaded using -agentpath like normal. It takes arguments in the
69 * `-Xplugin` and `-agentpath` need to be used, otherwise the agent will fail during init.
76 > `adb shell am start-activity --attach-agent /data/local/tmp/libtiallocsample.so=100 some.debug…
/art/test/
DAndroid.bp323 "ti-agent/agent_common.cc",
324 "ti-agent/agent_startup.cc",
325 "ti-agent/jni_binder.cc",
326 "ti-agent/jvmti_helper.cc",
327 "ti-agent/test_env.cc",
328 "ti-agent/breakpoint_helper.cc",
329 "ti-agent/common_helper.cc",
330 "ti-agent/early_return_helper.cc",
331 "ti-agent/frame_pop_helper.cc",
332 "ti-agent/locals_helper.cc",
[all …]
/art/tools/
Drun-prebuilt-libjdwp-tests.sh110 --agent-wrapper "${wrapper}"="${props_path}" \

12