Since it was found out in another topic that this actually is "KERN-EXEC 3" issue, it is very unlikely it is a UID problem.
What is more likely is that the application is crashing due to bug in it's code.
Since it was found out in another topic that this actually is "KERN-EXEC 3" issue, it is very unlikely it is a UID problem.
What is more likely is that the application is crashing due to bug in it's code.
There seems to be a little confusion. The original poster has been having similar issues over the year and half of development, and each time he opens new threads instead of referring to older threads. What happened in this thread was due to UID progably which he hasnt confirmed since, but what happens to his thread http://www.developer.nokia.com/Commu...ens#post883904 that he made fresh is something totally different...just guessing![]()
- Neil R.Bhasme -
Twitter: @Symbian_Neil
Sorry for not following the exact reason behind the panic error .
The present problem is After Installing the app , when clicked on the app icon nothing happens
In .hrh I gave as#define _UID3 0x2004aa20
In Application.h I gave as const TUid KUidPLACEADSApp =
{
0x2004aa20
};
In _reg.rsss I gave as
UID2 KUidAppRegistrationResourceFile
UID3 0x2004aa20
I have all the cerificate key pair, sis file given by nokia and instaled in the device too.
Didn't you tell in the other thread that the error was KERN-EXEC -3?
Yes teeemup but what should I do to solve that problem and remove that error
KERN-EXEC -3 can be debugged on emulator as well. Simply put debug points in ConstructL() of AppUi till its end & see where it crashes.
Do Remember to Search for your query on Google/Forum Wiki& DiBo , it really saves your time & You get your queries answered(in most of the cases) before posting them on Dibo itself. :)
How to put debug points in ConstructL()
I defined like this :
void CPLACEADSAppUi::ConstructL()
{
// Initialise app UI with standard value.
BaseConstructL(CAknAppUi::EAknEnableSkin);
// Create view object
iAppView = CPLACEADSAppView::NewL(ClientRect());
// Create a file to write the text to
TInt err = CCoeEnv::Static()->FsSession().MkDirAll(KFileName);
if ((KErrNone != err) && (KErrAlreadyExists != err))
{
return;
}
RFile file;
err = file.Replace(CCoeEnv::Static()->FsSession(), KFileName, EFileWrite);
CleanupClosePushL(file);
if (KErrNone != err)
{
CleanupStack::PopAndDestroy(1); // file
return;
}
RFileWriteStream outputFileStream(file);
CleanupClosePushL(outputFileStream);
outputFileStream << KText;
CleanupStack::PopAndDestroy(2); // outputFileStream, file
In your IDE which is carbide, simply click on left hand side of it where the code line number is written, on clicking a red/blue dot will appear which signifies a debug point. Hit the debug button from your IDE() & your application will then be started in debug mode(remember its emulator debug not device debug). Now your application points you to the various debug points(line by line) which you have set in the project.You start debug by pressing F6 from keyboard & keep pressing it for line by line jump of code, this way you can come to know that exactly on which line the code is crashing.
Do Remember to Search for your query on Google/Forum Wiki& DiBo , it really saves your time & You get your queries answered(in most of the cases) before posting them on Dibo itself. :)
probably checking Carbide.c++ help to see how to debug in emulator/device would help you. There may be guidelines in wiki too which could be searched.
- Neil R.Bhasme -
Twitter: @Symbian_Neil
How to avoid Panic KERN-EXEC 3 and why this panic occurs. How can I know where has the problem occured in the code?
when clciked on the application icon application is not starting what may be the valid reasons for such error?
Check out the KERN-EXEC panic docs here.
KERN-EXEC 3
This panic 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.
KERN-EXEC 3
This panic 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.