[Mono-bugs] [Bug 639030] On a Galaxy S (Samsung Vibrant) cached runtime is lost

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Oct 4 18:54:34 EDT 2010



Jonathan Pryor <jpryor at novell.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |NEEDINFO
                 CC|                            |jpryor at novell.com
       InfoProvider|                            |Novell-Bugzilla at bobf.franks
                   |                            |ton.com

--- Comment #1 from Jonathan Pryor <jpryor at novell.com> 2010-10-04 22:54:33 UTC ---
In general, division by zero isn't required.

An alternative way to ensure a process is killed is to open a terminal with the
Android SDK tools in the path, and:

> adb shell   # connects to the device
# ps          # look for your process name, e.g.
app_24    1040  30    160616 17932 ffffffff afe0da04 S mono.samples.hello

# kill 1040   # kill the PID from the above 'ps' line.

While you're in 'adb shell', you should see if the files have actually been
extracted, e.g.

# cd /data/data/mono.samples.hello  # use your.app.name
# ls
# ls files

The shared runtime files are stored in
/data/data/com.novell.monodroid.runtimeservice/files.  You should also ensure
that assemblies such as mscorlib.dll actually exist there.

'ls -l' will give full information such as file timestamp; it might be useful
to run 'ls -l' on the shared-runtime/files directory, then view the 'ls -l'
output again after restarting your app.  Are the timetamps continually updated?

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list