[android-developers] Re: stack corruption detected : aborted
Can you post some code for this? I am not sure if it's a bug in your
code, or the Android source.
-Kumar Bibek
http://techdroid.kbeanie.com
On Sep 6, 11:34 am, Nand wrote:
> Hi,
> I'm developing an application which connects to some agent running on
> desktop via Wi-Fi. After it connects and receives some data, stack
> corruption detected error encountered and gets aborted. I'm calling a
> recursive function for my data processing Can anyone please tell me
> what might be the problem? And also how to solve this issue?
>
> 09-06 11:11:51.517: ERROR/Common(537): 0 File:apps/Common/project/
> jni/per_decoder.c Line:39
> 09-06 11:11:51.517: ERROR/Common(537): 4555afd4 File:apps/Common/
> project/jni/per_decoder.c Line:48
> 09-06 11:11:51.517: ERROR/Common(537): 4555afd4 File:apps/Common/
> project/jni/per_decoder.c Line:63
> 09-06 11:11:51.517: ERROR/Common(537): 0 File:apps/Common/project/
> jni/per_decoder.c Line:66
> 09-06 11:11:51.517: ERROR/Common(537): 0 File:apps/Common/project/
> jni/per_decoder.c Line:71
> 09-06 11:11:51.517: ERROR/Common(537): 20 File:apps/Common/project/
> jni/per_decoder.c Line:75
> 09-06 11:11:51.517: ERROR/Common Exit(537): 20 File:apps/Common/
> project/jni/per_decoder.c Line:82
> 09-06 11:11:51.517: ERROR/Common Exit(537): [ 09-06 11:11:51.517
> 537:0x221 F/unknown ]
> 09-06 11:11:51.517: ERROR/Common Exit(537): stack corruption detected:
> aborted
> 09-06 11:11:51.546: INFO/WindowManager(61): WIN DEATH: Window{43b62e28
> com.android.manager/com.android.manager.Manager paused=false}
> 09-06 11:11:51.546: INFO/ActivityManager(61): Process
> com.android.manager (pid 537) has died.
> 09-06 11:11:51.596: DEBUG/Zygote(36): Process 537 terminated by signal
> (6)
> 09-06 11:11:51.636: INFO/UsageStats(61): Unexpected resume of
> com.android.settings while already resumed in com.android.manager
>
> Regards,
> Nand
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: stack corruption detected : aborted
Hi, Thanks for replying. I cant post the code as it is large application calling multiple functions at runtime. I'm also using native functions for thread creation and socket connection. If you can tell me the reasons for this issue to occur, I can look and try to check if any such exist in my application. Thanks in advance. Regards, Nand -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: stack corruption detected : aborted
Go through this link. It might help you. http://rxwen.blogspot.com/2009/04/detect-stack-corruption.html -Kumar Bibek http://techdroid.kbeanie.com On Sep 6, 12:06 pm, Nand wrote: > Hi, > Thanks for replying. > I cant post the code as it is large application calling multiple > functions at runtime. I'm also using native functions for thread > creation and socket connection. > > If you can tell me the reasons for this issue to occur, I can look and > try to check if any such exist in my application. > > Thanks in advance. > > Regards, > Nand -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: stack corruption detected : aborted
Perhaps you should instrument the depth of the recursion. And maybe limit it - would not be good if feeding a trick file to your app can crash or corrupt it. I made a wrapper for the android log vprint function that looks like a normal printf and sprinkle it liberally through my code, can simply turn it on or off at compile time. On Sep 6, 3:06 am, Nand wrote: > Hi, > Thanks for replying. > I cant post the code as it is large application calling multiple > functions at runtime. I'm also using native functions for thread > creation and socket connection. > > If you can tell me the reasons for this issue to occur, I can look and > try to check if any such exist in my application. > > Thanks in advance. > > Regards, > Nand -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
