Bug 575 - Application fails to start up
Summary: Application fails to start up
Status: RESOLVED FIXED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Portability (show other bugs)
Version: unreleased development snapshot
Hardware: ARM Android
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-07 21:07 CEST by notregistering
Modified: 2015-04-16 00:20 CEST (History)
1 user (show)



Attachments
Filtered logcat (7.49 KB, application/octet-stream)
2015-04-07 21:07 CEST, notregistering
Details
Logcat output (326.17 KB, text/plain)
2015-04-10 08:21 CEST, notregistering
Details

Note You need to log in before you can comment on or make changes to this bug.
Description notregistering 2015-04-07 21:07:12 CEST
Created attachment 133 [details]
Filtered logcat

I'm trying to use a nightly Android build from the website today.

My tablet is a Galaxy Tab S 8.4 running 4.4.2.  Not rooted or anything.

It looks like the application provides an instance of libglib2 which is linked
against libintl.so which is not provided by my tablet or the APK.

I'm attaching filtered logcat that shows the problem.
Comment 1 Uwe Hermann 2015-04-07 22:56:24 CEST
Hi, thanks for the report. This seems to be an issue related to libintl indeed.

I just checked that ndk-depends does indeed say that it cannot be found (when run on the extracted APK files from sigrok.org nightly builds).

$ {...]/ndk-depends libglib-2.0.so 
WARNING: Could not find library: libintl.so
libglib-2.0.so
libintl.so
libiconv.so
libdl.so
libc.so

I checked all .so files with ndk-depends, and only libintl.so is reported as "could not find" (multiple times though).
Comment 2 Uwe Hermann 2015-04-10 02:04:40 CEST
This is fixed in PulseView in 343f938f150becac42e8028f88783dc52d92eba0, with an additional fix in libsigrok b65630f78da2930fb828f6c6388c8655036fe8a4.

The current nightly build should work fine now (tested on an ARM tablet here). Thanks for the bug report, and please let us know if it works fine now for you!
Comment 3 notregistering 2015-04-10 08:09:12 CEST
(In reply to comment #2)
> This is fixed in PulseView in 343f938f150becac42e8028f88783dc52d92eba0, with
> an additional fix in libsigrok b65630f78da2930fb828f6c6388c8655036fe8a4.

It starts now but it crashed when I clicked `run' because it aborts:

I/DEBUG   ( 2288): backtrace:
I/DEBUG   ( 2288):     #00  pc 000222d0  /system/lib/libc.so (tgkill+12)
I/DEBUG   ( 2288):     #01  pc 000130dd  /system/lib/libc.so (pthread_kill+48)
I/DEBUG   ( 2288):     #02  pc 000132f1  /system/lib/libc.so (raise+10)
I/DEBUG   ( 2288):     #03  pc 00012027  /system/lib/libc.so
I/DEBUG   ( 2288):     #04  pc 00021b84  /system/lib/libc.so (abort+4)
I/DEBUG   ( 2288):     #05  pc 000893a4  /data/app-lib/org.sigrok.pulseview-1/libQt5Core.so (qt_message_fatal(QtMsgType, QMessageLogContext const&, QString const&)+24)
I/DEBUG   ( 2288):     #06  pc 00086390  /data/app-lib/org.sigrok.pulseview-1/libQt5Core.so (QMessageLogger::fatal(char const*, ...) const+92)

I'll attach filtered logcat output.
Comment 4 notregistering 2015-04-10 08:21:28 CEST
Created attachment 134 [details]
Logcat output

Logcat output from starting PulseView and clicking `run' which seemed to
cause PulseView to crash.

There is a stack trace and register dump.
Comment 5 Uwe Hermann 2015-04-12 16:07:48 CEST
It's strange, I could reproduce this issue (pressing "Run" on the demo driver cause PulseView to crash), but I retried the current APK as of today and can no longer reproduce the problem. I also tried two different logic analyzers, both worked fine on my tablet.

Could you retry as well please?
Comment 6 notregistering 2015-04-13 21:25:53 CEST
(In reply to comment #5)
> It's strange, I could reproduce this issue (pressing "Run" on the demo
> driver cause PulseView to crash), but I retried the current APK as of today
> and can no longer reproduce the problem. I also tried two different logic
> analyzers, both worked fine on my tablet.

It works for me now as well.

My LA does not, however, work but I'll try getting a log tomorrow and
see if it shows anything. I have granted PV permission to use the device,
and can find the device but is unable to start/select it.
Comment 7 Uwe Hermann 2015-04-15 16:29:40 CEST
> It works for me now as well.

OK, great!


> My LA does not, however, work but I'll try getting a log tomorrow and
> see if it shows anything. I have granted PV permission to use the device,
> and can find the device but is unable to start/select it.

Which LA do you try to use? If it needs firmware you have to copy that to your Android device into a certain directory.

See here for details:
http://sigrok.org/wiki/Android#Firmware_files
Comment 8 notregistering 2015-04-15 19:58:32 CEST
> Which LA do you try to use? If it needs firmware you have to copy that to
> your Android device into a certain directory.

Mine uses fx2lafw - it's a Saleae Logic 8 clone.

> See here for details:
> http://sigrok.org/wiki/Android#Firmware_files

OK, I misunderstood this then: "The APK ships PulseView for Android including all required libraries, protocol decoders, and so on."

I understood this as if the firmware was included.  I'll put it in there myself then and retry.

I think it'd be good to explicitly state if firmware is not supplied in the APK, btw.

Thanks for your work on sigrok and all your help!
Comment 9 notregistering 2015-04-16 00:20:38 CEST
> I understood this as if the firmware was included.  I'll put it in there
> myself then and retry.

It works now, thanks a lot!