CAknMultiLineDataQueryDialog does not launch in Mobile.

[aamitgupta]

Hi All,

I made a CAknMultiLineDataQueryDialog for username and password, that is working on Simulator but in mobile it is not open and our application exit, please help me.

[aamitgupta]

it gives error KERN-EXEC-3 when i click on login.

[sriky27]

Hi could you post your code please so that it would be easier

[symbianyucca]

No need to, just increase your Stack size, with default stack you will easily run out of stack, and this error is then generated.

[yogpan]

Hi All,

I made a CAknMultiLineDataQueryDialog for username and password, that is working on Simulator but in mobile it is not open and our application exit, please help me.

Hi,
Kern-Exec 3 means dereferencing a null pointer but as you said it is working fine is emulator i assume you would have already cross checked it.Another problem may be with the resource id which you are using for dialog, that is one point which you can look into whether you are putting the right resource file into the device.
Symbianyucca i have one doubt can we get Kern-Exec 3 because of stack size issue also. Please throw some light on this as i was not aware of this fact.

[symbianyucca]

No need to doubt, it is perfectly nice explanation that when you actually run out of stack you get memory violation error, which indeed is shown as Kern Exec 3.

In 3rd ed, it should be now well known fact that dialogs often fail to fit into the default stack size..

[kiran10182]

...i have one doubt can we get Kern-Exec 3 because of stack size issue also. Please throw some light on this as i was not aware of this fact.

One example: http://wiki.forum.nokia.com/index.ph...nt_Handler_API

[aamitgupta]

No need to doubt, it is perfectly nice explanation that when you actually run out of stack you get memory violation error, which indeed is shown as Kern Exec 3.

In 3rd ed, it should be now well known fact that dialogs often fail to fit into the default stack size..

yes yukka, thank when i increase the stacksize it is working.

Yukka can u help for sending WAP PUSH SMS.

[symbianyucca]

Yukka can u help for sending WAP PUSH SMS.

Never done that, but I would assume that maybe it could be done by making the message with correct bio type and sending it out. Though sending bio sms would then probably require networkcontrol & DiskAdmin capabilities.

Also since I have not tried it, I do not know details of the actual implementation, so could be indeed that it requires some other non-public APIs.

[yogpan]

No need to doubt, it is perfectly nice explanation that when you actually run out of stack you get memory violation error, which indeed is shown as Kern Exec 3.

In 3rd ed, it should be now well known fact that dialogs often fail to fit into the default stack size..

Hi,
Thanks symbianyucca that's one nice fact to know about the error and how it can be resolved!!!

[sriky27]

No need to doubt, it is perfectly nice explanation that when you actually run out of stack you get memory violation error, which indeed is shown as Kern Exec 3.

In 3rd ed, it should be now well known fact that dialogs often fail to fit into the default stack size..

That is an insight I donno that too thanks for information SymbianYucca

[aamitgupta]

Never done that, but I would assume that maybe it could be done by making the message with correct bio type and sending it out. Though sending bio sms would then probably require networkcontrol & DiskAdmin capabilities.

Also since I have not tried it, I do not know details of the actual implementation, so could be indeed that it requires some other non-public APIs.

So this is not possible through coding.

[symbianyucca]

So this is not possible through coding.

I did not say that, I said that I do not know, but you could try out whether it is possible.

[yogpan]

Hi,
The stuff should be possible programmatically its just the API required for it might not be available in public SDK so you will not have access to those information.The implementation is already there in S60 device so definitely it is possible only that it is available in native application and not for public usage.