search

MizanCSEJU / javacv

Automatically exported from code.google.com/p/javacv
GNU General Public License v2.0
0 stars 0 forks source link

Fatal signal 4 (SIGILL) at 0x5e776cec (code=1) #423

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. The following code reproduces the issue, and the server is not running.
Device : Samsung 10" GT-P7510
Android api : 4.0.4

if (yuvIplimage == null) {
  // Recreated after frame size is set in surface change method
  yuvIplimage = IplImage.create(imageWidth, imageHeight,
     IPL_DEPTH_8U, 2);

  Log.v(LOG_TAG, "IplImage.create");
}

Error under tag: libc: Fatal signal 4 (SIGILL) at 0x5e776cec (code=1)
Other logcat information, please find in the log attached.

Original issue reported on code.google.com by hearbeat...@gmail.com on 6 Feb 2014 at 11:07

Attachments:

GoogleCodeExporter commented 9 years ago 
The GT-P7510 is Tegra 2, so it looks like issue #366 hasn't been fixed. If you 
figure out how to build it so it doesn't crash, please post the details so I 
can fix it and make others benefit as well, thanks!

Original comment by samuel.a...@gmail.com on 6 Feb 2014 at 12:37

GoogleCodeExporter commented 9 years ago 
thank you for the merge. I didn't know what issue would be related to this. i 
am trying to find a fix for this from android side, if i succeed i will let you 
know, since i am a newbie when it comes to ndk and all.

Original comment by hearbeat...@gmail.com on 6 Feb 2014 at 12:46

GoogleCodeExporter commented 9 years ago 
Sir, If it is taking sometime to figure out how to solve this exception , is it 
possible to at least add a bit of code to the lib so that the exception can be 
caught in an android application (and then necessary actions taken at the 
android side) . Here is a link about how may be an exception could be covered 
in the jni itself. i am aware that you know better but just for reference as to 
how it might be captured in android then.

http://blog.httrack.com/blog/2013/08/23/catching-posix-signals-on-android/

Since, once the fatal signal error occurs, there is no exception that is thrown 
for the same. The cursor just returns, and the application stops.

Thanks .

Original comment by hearbeat...@gmail.com on 7 Feb 2014 at 10:50

GoogleCodeExporter commented 9 years ago 

Sir i have error shown below in the logcat while my application runs great but 
when i checked my application in the lolipop it shows this error on the 
genymotion emulator ,Please help me to resolve ,

11-28 07:38:56.891: W/OpenGLRenderer(2601): Failed to set EGL_SWAP_BEHAVIOR on 
surface 0xa58b67a0, error=EGL_SUCCESS

11-28 07:38:58.218: A/libc(2601): Fatal signal 4 (SIGILL), code 2, fault addr 
0xb6efe46e in tid 2620 (AsyncTask #2)

Original comment by abhishek...@sprytechies.com on 28 Nov 2014 at 7:44

GoogleCodeExporter commented 9 years ago 
@abhishek Crash in libc? That doesn't look like a problem with JavaCV. Please 
try to contact the authors of Android about that.

Original comment by samuel.a...@gmail.com on 6 Dec 2014 at 11:37

GoogleCodeExporter commented 9 years ago 
@samuel thanks but how could i contact to android authors

Original comment by abhishek...@sprytechies.com on 11 Dec 2014 at 5:45

GoogleCodeExporter commented 9 years ago 
@abhishek Right here: https://source.android.com/  BTW, make sure to use the 
x86 binaries if your device has an Intel processor.

Original comment by samuel.a...@gmail.com on 11 Dec 2014 at 7:24

GoogleCodeExporter commented 9 years ago 
thank you for your help

Abhishek Chaubey

Original comment by abhishek...@sprytechies.com on 11 Dec 2014 at 7:32

GoogleCodeExporter commented 9 years ago 
I have been getting a similar error when I try to decode a particular image 
file using the BitmapFactory,
'Fatal signal 4 (SIGILL) at 0x6635090c (code=1), thread 1712 (WebViewCoreThre)'
and then the app crashes

Original comment by trivikram.54 on 17 Mar 2015 at 6:31