Graphics, Gaming, and VR forum Why does Mali T880 does not support VK_EXT_debug_report extension?

State Accepted Answer
+1 person also asked this people also asked this
Locked Locked
Replies 3 replies
Subscribers 136 subscribers
Views 6078 views
Users 0 members are here

Options

Related

How was your experience today?

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why does Mali T880 does not support VK_EXT_debug_report extension?

Abhijit over 7 years ago

I am using Samsung Galaxy S7 edge with Android 6.0.1

Parents

0 Abhijit over 7 years ago in reply to Hans-Kristian Arntzen

Thanks. So it currently gives SIGSEV . Is the the expected behavior?

10-08 05:16:53.727 22838 23270 F libc	: Fatal signal 11 (SIGSEGV), code 2, fault addr 0xdfe23194 in tid 23270 (GLThread 1860)
10-08 05:16:53.747 3531 4195 D MdnieScenarioControlService: packageName : org.gearvrf.complexsScene	className : org.gearvrf.complexscene.SampleActivity

10-08 05:16:53.787 3158 3158 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

10-08 05:16:53.787 3158 3158 F DEBUG : Build fingerprint: 'samsung/hero2ltelgt/hero2ltelgt:6.0.1/MMB29K/G935LKLU1APH4:user/release-keys'

10-08 05:16:53.787 3158 3158 F DEBUG : Revision: '8'

10-08 05:16:53.787 3158 3158 F DEBUG : ABI: 'arm'

10-08 05:16:53.787 3158 3158 F DEBUG : pid: 22838, tid: 23270, name: GLThread 1860 >>> org.gearvrf.complexsScene <<<

10-08 05:16:53.787 3158 3158 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xdfe23194

10-08 05:16:53.817 3158 3158 F DEBUG :	r0 ee634b80 r1 de53f408 r2 00000000 r3 da26d0b8
10-08 05:16:53.817 3158 3158 F DEBUG :	r4 da26ca00 r5 dfe1357a r6 f70ceec0 r7 dfe23194
10-08 05:16:53.817 3158 3158 F DEBUG :	r8 dfe23144 r9 dfe23188 sl 00000000 fp 00000000
10-08 05:16:53.817 3158 3158 F DEBUG :	ip de53efe4 sp de53f408 lr dfdba851 pc dfe23194 cpsr 60070010

10-08 05:16:53.827 3158 3158 F DEBUG :

10-08 05:16:53.827 3158 3158 F DEBUG : backtrace:

10-08 05:16:53.827 3158 3158 F DEBUG :	#00 pc 00000194 /data/app/org.gearvrf.complexsScene-1/lib/arm/libgvrf.so (offset 0x114000)
10-08 05:16:53.827 3158 3158 F DEBUG :	#01 pc 000ac84f /data/app/org.gearvrf.complexsScene-1/lib/arm/libgvrf.so (_ZN3gvr10VulkanCore25CreateValidationCallbacksEv+174)
10-08 05:16:53.827 3158 3158 F DEBUG :	#02 pc 000af4a3 /data/app/org.gearvrf.complexsScene-1/lib/arm/libgvrf.so (_ZN3gvr10VulkanCore14initVulkanCoreEP1

Reply

0 Abhijit over 7 years ago in reply to Hans-Kristian Arntzen

Thanks. So it currently gives SIGSEV . Is the the expected behavior?

10-08 05:16:53.727 22838 23270 F libc	: Fatal signal 11 (SIGSEGV), code 2, fault addr 0xdfe23194 in tid 23270 (GLThread 1860)
10-08 05:16:53.747 3531 4195 D MdnieScenarioControlService: packageName : org.gearvrf.complexsScene	className : org.gearvrf.complexscene.SampleActivity

10-08 05:16:53.787 3158 3158 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

10-08 05:16:53.787 3158 3158 F DEBUG : Build fingerprint: 'samsung/hero2ltelgt/hero2ltelgt:6.0.1/MMB29K/G935LKLU1APH4:user/release-keys'

10-08 05:16:53.787 3158 3158 F DEBUG : Revision: '8'

10-08 05:16:53.787 3158 3158 F DEBUG : ABI: 'arm'

10-08 05:16:53.787 3158 3158 F DEBUG : pid: 22838, tid: 23270, name: GLThread 1860 >>> org.gearvrf.complexsScene <<<

10-08 05:16:53.787 3158 3158 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xdfe23194

10-08 05:16:53.817 3158 3158 F DEBUG :	r0 ee634b80 r1 de53f408 r2 00000000 r3 da26d0b8
10-08 05:16:53.817 3158 3158 F DEBUG :	r4 da26ca00 r5 dfe1357a r6 f70ceec0 r7 dfe23194
10-08 05:16:53.817 3158 3158 F DEBUG :	r8 dfe23144 r9 dfe23188 sl 00000000 fp 00000000
10-08 05:16:53.817 3158 3158 F DEBUG :	ip de53efe4 sp de53f408 lr dfdba851 pc dfe23194 cpsr 60070010

10-08 05:16:53.827 3158 3158 F DEBUG :

10-08 05:16:53.827 3158 3158 F DEBUG : backtrace:

10-08 05:16:53.827 3158 3158 F DEBUG :	#00 pc 00000194 /data/app/org.gearvrf.complexsScene-1/lib/arm/libgvrf.so (offset 0x114000)
10-08 05:16:53.827 3158 3158 F DEBUG :	#01 pc 000ac84f /data/app/org.gearvrf.complexsScene-1/lib/arm/libgvrf.so (_ZN3gvr10VulkanCore25CreateValidationCallbacksEv+174)
10-08 05:16:53.827 3158 3158 F DEBUG :	#02 pc 000af4a3 /data/app/org.gearvrf.complexsScene-1/lib/arm/libgvrf.so (_ZN3gvr10VulkanCore14initVulkanCoreEP1

Children

0 Peter Harris over 7 years ago in reply to Abhijit

Based on the backtrace the segfault is in the application code, so I'm not sure why we would know if it's the expected behavior or not - it isn't our code ...
HTH,
Pete
Cancel
Up 0 Down

Cancel