diff options
| author | Alex Light <allight@google.com> | 2020-09-22 15:35:59 -0700 |
|---|---|---|
| committer | Treehugger Robot <treehugger-gerrit@google.com> | 2020-10-02 18:58:58 +0000 |
| commit | 8d9c6048caa5ac3051e05540c04ea7cb3dfff9a7 (patch) | |
| tree | e18df218572fc3d745af384ccfa5308a352239ae /test/ProfileTestMultiDex/Main.java | |
| parent | 8b247625f58ba8a0f616594dc774089678aa57e3 (diff) | |
Add test for thread-attach naming behavior
The interaction between pthread_setname_np and AttachCurrrentThread is
not always obvious. Add a test to codify the interaction. Basically
AttachCurrentThread will always override the current
pthread_setname_np thread name, including if AttachCurrentThread is
called without an explicit name, in which case the pthread-name will
be changed to the name selected by java.
Test: ./test.py --host
Bug: 168655382
Change-Id: If0319b733dc808a4cb892b6199030657c3e69f81
Diffstat (limited to 'test/ProfileTestMultiDex/Main.java')
0 files changed, 0 insertions, 0 deletions