Discussion:
bl AAssetManager_fromJava causing sigbus
(too old to reply)
m***@gmail.com
2018-10-04 17:47:34 UTC
Permalink
I have been developing an android NDK forth library for quite a while now
and while it used to work it no longer does due to changes made to
android. For the past couple of weeks I have been performing major surgery
on my source and am in the process of debugging things.

One by one I was knocking bugs out and added a log printf to some code
beyond my lst fix and suddenly some other section of the code that had
previously been debugged and working is now causing a sigbus. Removal of
the printf did not fix it. it worked (up to a point), i made an edit, it
failed in previously working code, i undid the edit, it fails still.

One of the things that needs to be done in the java that uses my library is
that it needs to pass the asset manager to the NDK code. I have an init
function to handle this which is extremely trivial...

init:
mov r1, r2
bl AAssetManager_fromJava
..

the above call causes a sigbus where as previously it was not doing so.
What could possibly cause this call to fault in this way?

I cant show the code, its not for release which I know will make it much
more difficult for you to help me :/
--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ndk+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-ndk.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/2122ef3e-3fa7-4605-83c6-2ed5911f32b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...