Issue https://github.com/golang/go/issues/25035 "runtime: android 
backtraces do not include go backtrace" was filed long back. It is 
reproducible and here is an example of the results. In my limited 
understanding, there are two issues here. 

1. Backtrace includes just one entry rather than all the stack entries 
2. The more readable stacktrace coming from panic is being logged at 
[E]rrorand not [F]atal level.

I did see some revelant code 
at https://github.com/golang/go/blob/master/src/runtime/cgo/gcc_android.c 
but that does not seem to trigger even if I do log.Fatalf

Is there a way to fix (1) or (2) or preferably both? Can someone guide me 
as to where to go about debugging this?


02-28 10:23:37.550 20240     0 E Go      : panic: TODO(ashishb): testing 
only
02-28 10:23:37.550 20240     0 E Go      :
02-28 10:23:37.550 20240     0 E Go      : goroutine 8 [running]:
02-28 10:23:37.551 20240     0 E Go      : main.onDraw(0xca1f5780, 
0x998d80b0, 0x5a0, 0x958, 0x43392492, 0x4399c57c, 0x40f8e38e, 0x1)
02-28 10:23:37.551 20240     0 E Go      :  
/Users/ashishb/src/gomobile/example/network/main.go:114 
+0x31
02-28 10:23:37.551 20240     0 E Go      : main.main.func2(0xca1f4bc0, 
0xca3684a0)
02-28 10:23:37.551 20240     0 E Go      :  
/Users/ashishb/src/gomobile/example/network/main.go:89 
+0x1d0
02-28 10:23:37.551 20240     0 E Go      : 
golang.org/x/mobile/app.mainUI.func1(0x998460c0)
02-28 10:23:37.551 20240     0 E Go      :  
/Users/ashishb/go/src/golang.org/x/mobile/app/android.go:288 
+0x3f
02-28 10:23:37.551 20240     0 E Go      : created by 
golang.org/x/mobile/app.mainUI
02-28 10:23:37.552 20240     0 E Go      :  
/Users/ashishb/go/src/golang.org/x/mobile/app/android.go:287 
+0x7e
02-28 10:23:37.552 20240 20267 F libc    : Fatal signal 6 (SIGABRT), code 
-6 (SI_TKILL) in tid 20267 (ng.todo.network), pid 20240 (ng.todo.network)
02-28 10:23:37.588 20270 20270 I crash_dump32: obtaining output fd from 
tombstoned, type: kDebuggerdTombstone
02-28 10:23:37.589  3831  3831 I /system/bin/tombstoned: received crash 
request for pid 20267
02-28 10:23:37.590 20270 20270 I crash_dump32: performing dump of process 
20240 (target tid = 20267)
02-28 10:23:37.596 20270 20270 F DEBUG   : *** *** *** *** *** *** *** *** 
*** *** *** *** *** *** *** ***
02-28 10:23:37.596 20270 20270 F DEBUG   : Build fingerprint: 
'google/sdk_gphone_x86/generic_x86:9/PSR1.180720.061/5075414:userdebug/dev-keys'
02-28 10:23:37.596 20270 20270 F DEBUG   : Revision: '0'
02-28 10:23:37.596 20270 20270 F DEBUG   : ABI: 'x86'
02-28 10:23:37.596 20270 20270 F DEBUG   : pid: 20240, tid: 20267, name: 
ng.todo.network  >>> org.golang.todo.network <<<
02-28 10:23:37.596 20270 20270 F DEBUG   : signal 6 (SIGABRT), code -6 
(SI_TKILL), fault addr --------
02-28 10:23:37.596 20270 20270 F DEBUG   :     eax 00000000  ebx 00004f2b  
ecx 00000006  edx 00000000
02-28 10:23:37.596 20270 20270 F DEBUG   :     edi 00000001  esi 00000008
02-28 10:23:37.596 20270 20270 F DEBUG   :     ebp 00000020  esp 99821e5c  
eip c9f765e7
02-28 10:23:37.597 20270 20270 F DEBUG   :
02-28 10:23:37.597 20270 20270 F DEBUG   : backtrace:
02-28 10:23:37.597 20270 20270 F DEBUG   :     #00 pc 000be5e7  
/data/app/org.golang.todo.network-qF6PD3_ANDgUrZW8Ly0osQ==/lib/x86/libnetwork.so
 
(runtime.raise+23)

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to