kern-exec 3 problem

[noam segal]

Hi

When I close my application using iAppUi->Exit() I gets kern-exec 3 panic.
I tried to put break point in the app ui destructor but it doesn't get there yet.

Regards,
Noam

[lucky@symbian]

can u please share ur IDE and Platform information.

[noam segal]

Hi

carbide.c 1.2.2 s60 3rd_MR

hope it helps.

Noam

[wizard_hu_]

If it happens in the emulator, you should enable Just In Time debugging in the preferences. Then you will get a break when the panic occurs, and you will quickly find the problematic code in the call stack.

[isarc]

kern-exec 3 error often be caused by pointer, look careful at your pointer, not new,not delete, should not be deleted.....

[pavanmv]

Generally you get the KernExec-3 panic, if your application has not released all the resources ( RClass handles ) or freed heap based objects when trying to terminate. Check your dtor.

[wizard_hu_]

Generally you get the KernExec-3 panic, if your application has not released all the resources ( RClass handles ) or freed heap based objects when trying to terminate. Check your dtor.

It is just not true. KERN-EXEC 3 is typically the "NULL panic", however it has other meanings as well.
The basic "leak panic" is the ALLOC for example.

[pavanmv]

Hi,

Yeah i agree its not completely true but does happen sometimes.
Another issue this can occur is in case of stack overflow.

Here is a transcript from device creators doclib

Warning: stack overflow == KE3
Always be aware to check whether you’re suffering from a stack overflow
A stack overflow will cause unexplainable KERN-EXEC 3 errors

[lucky@symbian]

Generally you get the KernExec-3 panic, if your application has not released all the resources ( RClass handles ) or freed heap based objects when trying to terminate. Check your dtor.

We dont get a KERN-EXEC3 for improper heap deallocation, we get Alloc panics.

KERN-EXEC3 is raised when an unhandled exception occurs. Exceptions have many causes, but the most common are access violations caused, for example, by dereferencing NULL. Among other possible causes are: general protection faults, executing an invalid instruction, alignment checks, etc.
Stack overflow should fit into protection faults category.

[pavanmv]

Hey i am really sorry, in my previous post i was referring to Kern exec 0.

Another reason you could end up with a Kern-Exec 3 when you are exiting the application, is when you have registered a view and manually try deleting it. This is because the view server will takecare of deletion of the views, if you have explictly deleted it, then when the view server tries to delete the same, it will end up with a Kern-Exec 3

[sarae]

Hi pavanmv! Thanks so much, that was exactly the right advice for me. I deleted my view manually...

[nokia_wangyu]

If it happens in the emulator, you should enable Just In Time debugging in the preferences. Then you will get a break when the panic occurs, and you will quickly find the problematic code in the call stack.

Could you please give me some information, help me to enable Just In Time debugging in the preferences?
Thanks very much!!

[nehasaxena]

you can use User::Exit(0) instead of only exit.

[nokia_wangyu]

you can use User::Exit(0) instead of only exit.

I'm afraid it's unsuitable.

Exit() is the function of CAknAppUiBase.

AppFrame will do some cleanning works.

[nokia_wangyu]

Could you please give me some information, help me to enable Just In Time debugging in the preferences?
Thanks very much!!

Does anyone know how to use 'Just In Time debugging '?

thank for your response.