A andrewj Active Member Licensed User Longtime User Feb 20, 2014 #1 Hi, I'm getting the following error occasionally in the log, at which point my app crashes: Fatal signal 11 (SIGSEGV) at 0x002e0069 (code=1), thread 25768 (andrewj.stashit) Any idea how I track the cause? Thanks Andrew
Hi, I'm getting the following error occasionally in the log, at which point my app crashes: Fatal signal 11 (SIGSEGV) at 0x002e0069 (code=1), thread 25768 (andrewj.stashit) Any idea how I track the cause? Thanks Andrew
JordiCP Expert Licensed User Longtime User Feb 20, 2014 #2 This signal is related to some kind invalid memory access. Look here Are you developing any library or have you added recently a new one to your project? I faced it several times when developing one and it was hard to track at least in my case. The unfiltered logs previous to when it happens would help . Also, a rude but effective approach is to add log messages in different parts of the b4a program in order to isolate it. But if it is caused by something performed asynchronously in a different thread it will be no use. Upvote 0
This signal is related to some kind invalid memory access. Look here Are you developing any library or have you added recently a new one to your project? I faced it several times when developing one and it was hard to track at least in my case. The unfiltered logs previous to when it happens would help . Also, a rude but effective approach is to add log messages in different parts of the b4a program in order to isolate it. But if it is caused by something performed asynchronously in a different thread it will be no use.
A andrewj Active Member Licensed User Longtime User Feb 20, 2014 #3 Thanks. I think it may be related to the GestureDetector library which has not be fully set up for the new debugging model, but it might also be the way I have set my tablet for image operations. I'll progress with your logging idea and see where that goes. Thanks Andrew Upvote 0
Thanks. I think it may be related to the GestureDetector library which has not be fully set up for the new debugging model, but it might also be the way I have set my tablet for image operations. I'll progress with your logging idea and see where that goes. Thanks Andrew
JordiCP Expert Licensed User Longtime User Feb 20, 2014 #4 The new debugger does not work well in all situations, for these cases I use the legacy one Upvote 0
