Home
last modified time | relevance | path

Searched refs:events (Results 1 – 25 of 37) sorted by relevance

12

/art/test/1962-multi-thread-events/
Dmulti_thread_events.cc34 jobject events; member
55 env->CallStaticVoidMethod(klass, handler, thread, data->events); in cbMethodEntry()
73 JNIEnv* env, jclass klass ATTRIBUTE_UNUSED, jthread thr, jobject events, jobject target) { in Java_art_Test1962_setupThread() argument
79 data->events = env->NewGlobalRef(events); in Java_art_Test1962_setupThread()
DAndroid.bp3 name: "art-run-test-1962-multi-thread-events",
Dinfo.txt5 could cause events to be missed.
/art/tools/jvmti-agents/ti-fast/
DREADME.md4 to various JVMTI events. It is called tifast since none of the event handlers do
26 * If 'all' is one of the arguments all events the current runtime is capable of
34 those needed to listen for the events are gained.
36 * Only events which do not require additional function calls to cause delivery
39 #### Supported events
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
96 events either require the use of other functions in order to be called
/art/test/1933-monitor-current-contended/
Dinfo.txt1 Tests jvmti monitor events in odd situations.
3 Checks that the JVMTI monitor events are correctly dispatched and handled for
/art/test/1932-monitor-events-misc/
Dinfo.txt1 Tests jvmti monitor events in odd situations.
3 Checks that the JVMTI monitor events are correctly dispatched and handled for
DAndroid.bp3 name: "art-run-test-1932-monitor-events-misc",
/art/test/1919-vminit-thread-start-timing/
Dvminit.cc45 std::vector<EventData> events; member
62 list->events.push_back({ "ThreadStart", env->NewGlobalRef(thread) }); in ThreadStartCallback()
74 list->events.push_back({ "Test1919AgentThread", env->NewGlobalRef(cur) }); in Test1919AgentThread()
112 list->events.push_back({ "VMInit", env->NewGlobalRef(thread) }); in VMInitCallback()
165 jobjectArray ret = CreateObjectArray(env, list->events.size(), "java/lang/String", in Java_art_Test1919_getEventNames()
167 return env->NewStringUTF(list->events[i].event.c_str()); in Java_art_Test1919_getEventNames()
186 jobjectArray ret = CreateObjectArray(env, list->events.size(), "java/lang/Thread", in Java_art_Test1919_getEventThreads()
188 return env->NewLocalRef(list->events[i].data); in Java_art_Test1919_getEventThreads()
Dinfo.txt3 Test the interaction of VMInit events and thread starts.
/art/test/991-field-trace-2/
Dinfo.txt4 while handling these events. It also verifies the situations in which these
5 events are sent.
/art/test/1962-multi-thread-events/src/art/
DTest1962.java34 public static void HandleEvent(Thread t, List<String> events) { in HandleEvent() argument
35 events.add("Hit event on " + t.getName()); in HandleEvent()
82 public static native void setupThread(Thread t, List<String> events, Method target); in setupThread() argument
/art/runtime/
Dinstrumentation.cc558 static bool HasEvent(Instrumentation::InstrumentationEvent expected, uint32_t events) { in HasEvent() argument
559 return (events & expected) != 0; in HasEvent()
563 uint32_t events, in PotentiallyAddListenerTo() argument
569 if (!HasEvent(event, events)) { in PotentiallyAddListenerTo()
583 void Instrumentation::AddListener(InstrumentationListener* listener, uint32_t events) { in AddListener() argument
586 events, in AddListener()
591 events, in AddListener()
596 events, in AddListener()
601 events, in AddListener()
606 events, in AddListener()
[all …]
/art/test/1941-dispose-stress/
Dinfo.txt3 Ensures that we can receive single step events from JVMTI.
/art/test/997-single-step/
Dinfo.txt3 Ensures that we can receive single step events from JVMTI.
/art/test/1927-exception-event/
Dinfo.txt3 Ensures that we can receive exception and exception catch events from JVMTI.
/art/test/1931-monitor-events/
Dinfo.txt3 Tests that the basic monitor-events work as we expect them to.
DAndroid.bp3 name: "art-run-test-1931-monitor-events",
/art/test/933-misc-events/
DAndroid.bp3 name: "art-run-test-933-misc-events",
/art/tools/jvmti-agents/list-extensions/
Dlist-extensions.cc126 jvmtiExtensionEventInfo* events = nullptr; in SetupJvmtiEnv() local
127 if (env->GetExtensionEvents(&n_ext, &events) != JVMTI_ERROR_NONE) { in SetupJvmtiEnv()
132 const jvmtiExtensionEventInfo& info = events[i]; in SetupJvmtiEnv()
145 Dealloc(env, events); in SetupJvmtiEnv()
/art/test/1936-thread-end-events/
DAndroid.bp3 name: "art-run-test-1936-thread-end-events",
Dinfo.txt3 We had a bug where we were still sending events after JVMTI_EVENT_THREAD_END due
/art/test/1947-breakpoint-redefine-deopt/
Dinfo.txt5 paths and then runs the function, receiving the breakpoint events.
/art/test/995-breakpoints-throw/
Dinfo.txt3 Tests that it is possible to throw exceptions while handling breakpoint events
/art/test/994-breakpoint-line/
Dinfo.txt5 paths and then runs the function, receiving the breakpoint events.
/art/test/1940-ddms-ext/
Dddm_ext.cc217 jvmtiExtensionEventInfo* events = nullptr; in Java_art_Test1940_initializeTest() local
218 if (JvmtiErrorToException(env, jvmti_env, jvmti_env->GetExtensionEvents(&n_ext, &events))) { in Java_art_Test1940_initializeTest()
222 jvmtiExtensionEventInfo* cur_info = &events[i]; in Java_art_Test1940_initializeTest()
232 Dealloc(events); in Java_art_Test1940_initializeTest()

12