Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SilentUpdate Segmentation fault #54

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

Hi, 

I have a problems using SilentAutoUpdate running a Testapp on a rooted android 
Box(not a mobile).

I'm testing with android 4.2.2 and auto-update-apk-client_2012-10-04.tgz

When I upload a new version of my Testapp over the web UI, I notice that the 
AutoUpdateApk detects it but latter in the execution I get:

E/AutoUpdateApk( 1513): Segmentation fault 
E/AutoUpdateApk( 1513): Segmentation fault (139)  

The old version of the apk keeps running and in the the shared_prefs file the 
parameter "update_file" has been changed to the new versions name.

I'am attaching a logcat trace and a zip file with my test app. Thank you.


BR
Alex


Original issue reported on code.google.com by a.kiri...@gmail.com on 29 Nov 2013 at 3:51

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

this is most probably related to the wrong/invalid version of 'su' utility 
installed on your box.

1. could you please check if the non-Silent version of AutoUpdateAPK runs or 
fails on your particular system?

2. if the non-silent version runs just fine, please, try to run 'su' commands 
from the command line and see if something fails.

3. if 'su' works well from the command line, please, try to issue the same 
commands used in the source code to install and replace the .apk with the new 
one. also, you may try to comment out these commands in the source code and see 
if you get a 'segmentation fault'.

Original comment by lenik.terenin on 30 Nov 2013 at 4:38

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

The problem is that 'su' command is not working really fine on the box, so I 
tried 'busybox su' which is returning "su: unknown user root".
Using it in the test app I get : 
V/AutoUpdateApk(32703): got a reply from update server
V/AutoUpdateApk(32703): got a package from update server
V/AutoUpdateApk(32703): update check finished in 1549ms
V/AutoUpdateApk(32703): md5sum: 8c94ef0b1ff55fc23e4d6fea5423abfc
I/AutoUpdateApk(32703): LD_LIBRARY_PATH=/vendor/lib:/system/lib pm install -r 
/data/data/net.kirilov.autoupdatetest/files/AutoupdateTest_5.apk
E/AutoUpdateApk(32703): write failed: EPIPE (Broken pipe)


I think that i have root access over the shell because over the shell the 
update works fine,  but not from the app. The app process runs under different 
user, not root. Is there something I can do about? Thank you.

Original comment by a.kiri...@gmail.com on 2 Dec 2013 at 2:15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.