0% found this document useful (0 votes)
22 views2 pages

Not Bad

The document contains the arguments and environment variables used to launch an Exagear virtual machine instance on an Android device. It launches the Exagear virtualization platform with arguments to specify paths, configuration files, and programs to run inside the virtual machine instance. The launched programs include a Windows Explorer shell and a TFM application.

Uploaded by

Yanz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views2 pages

Not Bad

The document contains the arguments and environment variables used to launch an Exagear virtual machine instance on an Android device. It launches the Exagear virtualization platform with arguments to specify paths, configuration files, and programs to run inside the virtual machine instance. The launched programs include a Windows Explorer shell and a TFM application.

Uploaded by

Yanz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

argv = ['libubt'; '--vfs-kind'; 'guest-first'; '--path-prefix';

'/data/user/0/com.eltechs.eg/files/image'; '--vpaths-list';
'/data/user/0/com.eltechs.eg/files/image/.exagear/vpaths-list'; '-f';
'/opt/recipe/run/simple.sh'; '--fork-controller'; 'ua:.exagear-tracker-app12'; '--
ipc-emul-server'; 'ua:com.eltechs.eg'; '--tmp-dir';
'/data/user/0/com.eltechs.eg/files/image/.exagear/tmp'; '--vfs-
hacks=tlsasws,tsi,spd,'; '--socket-path-suffix'; 'ed'; '--ubt-executable';
'/data/app/~~qYV3au0VcR2WzPkSx-Lgyg==/com.eltechs.eg-0mA2zxTvdAjsa34al10a1g==/lib/
arm/libubt.so'; '--ubt-loader';
'/data/app/~~qYV3au0VcR2WzPkSx-Lgyg==/com.eltechs.eg-0mA2zxTvdAjsa34al10a1g==/lib/
arm/libelfloader.so'; '--'; '/opt/recipe/run/simple.sh'; 'eval "wine explorer
/desktop=shell,1920x1080 /opt/exec_wrapper.exe /opt/TFM.exe D:/"'; ]
envp = ['HOME=/home/xdroid/'; 'WINEPREFIX=/home/xdroid/.wine'; 'LC_ALL=en_US.utf8';
'GALLIUM_DRIVER=llvmpipe'; 'DISPLAY=:12'; 'AXS_SOUND_SERVER_PORT=/tmp/.sound/AS12';
'AXS_DSOUND_SERVER_PORT=/tmp/.sound/DS12'; ]
cwd = '/storage/emulated/0/Download'
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
0050:err:ole:start_rpcss Failed to open RpcSs service
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
0024:err:ole:start_rpcss Failed to open RpcSs service
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
0050:err:ole:start_rpcss Failed to open RpcSs service
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
00c0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01BBFEF8
00f8:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 02A9FEF8
00d0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01FFFEF8
00c4:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01CCFEF8
00d4:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0210FEF8
00c8:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01DDFEF8
00d8:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0221FEF8
00dc:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0232FEF8
00ec:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0276FEF8
00e0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0243FEF8
00fc:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 02BAFEF8
00e4:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0254FEF8
00f0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0287FEF8
00f4:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0298FEF8
00cc:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01EEFEF8
00e8:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0265FEF8
00bc:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
shared memfd open() failed: Function not implemented
0110:fixme:winmm:MXD_GetControlDetails What should the sw-side mixer controls map
to?
0110:fixme:winmm:MXD_SetControlDetails What should the sw-side mixer controls map
to?
wine: Unhandled page fault on read access to 00000000 at address 0CDC95A9 (thread
00bc), starting debugger...
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
Xlib: extension "SHAPE" missing on display ":12".
014c:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 017AFEF8
0170:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0213FEF8
0168:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01F1FEF8
016c:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0202FEF8
0174:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0224FEF8
0164:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01E0FEF8
0150:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 018BFEF8
013c:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0136FEF8
0144:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0158FEF8
0154:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 019CFEF8
015c:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01BEFEF8
0160:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01CFFEF8
0138:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0125FEF8
0158:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01ADFEF8
0140:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0147FEF8
0148:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0169FEF8
0134:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
shared memfd open() failed: Function not implemented
0188:fixme:winmm:MXD_GetControlDetails What should the sw-side mixer controls map
to?
0188:fixme:winmm:MXD_SetControlDetails What should the sw-side mixer controls map
to?

You might also like