-
KERN-EXEC Panic
Hi All,
I have created an application with views, CEikTextListBox controls and a host of other controls. When I change the orientation of the screen, my application crashes and the emulator shows the following error - "App. close: ApplicationName KERN-EXEC 3". I have no clue as to how and where to begin debuggin this problem. Is there a way to find out which statement is causing this problem? Please help.
Thanks,
Shanker
-
Re: KERN-EXEC Panic
Have u checked ur callstack . kernexec3 comes when u r trying to work on a null pointer.
Thanks
-
Re: KERN-EXEC Panic
Hello,
when you change orientation of the screen CCoeControl calls HandleResourceChange(TInt aType) function.
I think you should start searching for the reason of error there.
Some part of your code pasted here would make it easier to solve it :)
Good luck
-
Re: KERN-EXEC Panic
Hi Kishore84,
How do i get the callstack??
I am using Carbide.c++ v 1.3 express edition.
Thanks,
Shanker
-
Re: KERN-EXEC Panic
on carbide it is very simple . just go to the debug mode (go to windows->openperspective->debug...). then u can see ur call stack.otherwise at right corner u could find to switch to various mode like debug, carbide c++.....
Thanks
-
Re: KERN-EXEC Panic
Hi Kishore,
I added the following code to my applications AppUI -
void CVAppUi::HandleResourceChangeL(TInt aType)
{
// CAknViewAppUi::HandleResourceChangeL(aType);
//
// if (aType == KEikDynamicLayoutVariantSwitch)
// {
// iAppView->SetRect(ClientRect());
// }
}
You may notice some of the code commented. If the code is uncommented my application crashes showing KERN-EXEC 3 error, otherwise, I am able to switch from portrait to landscape view, and vice versa, but my screen look broken and incomplete. How do I redraw screen? Please help.
Thanks,
Shanker
-
Re: KERN-EXEC Panic
If you enable "Just In Time debugging" in emulator preferences, it will show the exact location of the crash.
Since your iAppView is most probably not NULL (though you can check it for making sure), the next thing to check would be SizeChanged method of your AppView object. But it is easier letting the debugger to catch the panic.