my ui application contains 44 pages.it runs fine but sometime get crash while running.
the simulator closes on crash.
my ui application contains 44 pages.it runs fine but sometime get crash while running.
the simulator closes on crash.
if you could run it on a device, you could at least get the panic code for the crash: http://wiki.forum.nokia.com/index.ph...ded_panic_code it could maybe tell something about the reason. Also you could try whether you could pinpoint the actual problem, by checking whther the crash is repeatable, and if it is, then you could try checking on what is actually be done when you get the crash.
thank you symbianyucca.
Last edited by harshalsengar; 2011-04-22 at 05:47.
Actully i am using Qt Creator.I am trying to find the directory in the given link but din't find.
How would i know the panic code there.
actually that idea was only for devices and if you are using the sdk the best way would be to keep break points and then test the application where you are getting the crash, that will help you to know where you are exactly getting the error and why.
Regards
Gargi Das- http://gargidas.blogsot.com
Forum Nokia Python Wiki
Learn Python at http://mobapps.org/PyS60
i am running application on device.And the application not crashes on particular.
during run the screen suddenly become black.
thats because your application in going out of heap memory this is atleast what my experience tells, try increasing the heap memory or change your implementation which uses lots of memory at heap.
Gargi Das- http://gargidas.blogsot.com
Forum Nokia Python Wiki
Learn Python at http://mobapps.org/PyS60
"\$(CODE_SEGMENT_START) ", "\$(DATA_SEGMENT_START) 0xA00000 "
"\$(CODE_SEGMENT_START) ", "\$(DATA_SEGMENT_START) 0xA00000 "
i used this in my cl_bpabi.pm
hello to all.....
could you please tell me that, where i can find the "qtsoap" implimentation knowledge for symbian.
Get more knowledge about Qtsoap.
- AbhisheKhetani
hello danhicksbyron,
thanks for reply,
can u tell me the another solution.
Well, you need to figure out why it's crashing. Odds are, it's either running out of heap (possibly due to a leak, possibly just too much stuff), or it's encountering an addressing fault (usually due to "dangling pointers").
FIrst thing to do is to monitor heap size as the application runs.
But if this is the simulator, and the entire simulator is going "poof", then it's more likely some sort of addressing fault. The simulator doesn't handle these very well.
Black images on the screen, on the other hand, is a sure sign of running out of heap.