11-16-2012 01:33 AM - edited 11-16-2012 01:35 AM
Please tell how to trace down the Application not responding errors---
e.g in my logs i can see --
MyApp(277) 105 2 0x19913400 net_rim_cldc-2(4C48DD41) TimerThread <private> 0xB0DA net_rim_cldc-2(4C48DD41) TimerThread run 0xAFE8
ForcedStackTraceException MyApp(277) 169 1 net_rim_cldc-32(4C48DD41) DebugSupport logStackTraces 0xC9D net_rim_cldc-10(4C48DD41) ApplicationProcess logMessageQueueOverflow 0x44B0 net_rim_cldc-10(4C48DD41) ApplicationProcess postMessage 0x41FD net_rim_cldc-10(4C48DD41) ApplicationManagerImpl <private> 0x1E60
So i wanted to know what the numbers indicates in --MyApp(277) 166 1 -----line
Thanks in advance.
11-16-2012 03:42 AM
11-16-2012 04:11 AM
Thanks simon. Actually i was waiting for ur reply.
The link given seems very useful to my problem.I will review my code and hopefully will get over the problem.
But one more thing that kept me interested is that---
When i checked the logs--i found different number in front of each trace e.g .
---MyApp(277) 166 1
---MyApp(277) 166 2
--MyApp(277) 166 4
--MyApp(277) 166 5
is there is any information with these numbers regarding which thread may cause the problem??
11-16-2012 04:42 AM
I have always presumed that each of these was a separate Thread and the numbering was just to distinguish them. Probably wrong.....
Never used these numbers to work on this sort of problem, I just look for the Thread that is running the Event Thread (look at the last entry in the stack trace to see your Application's main() and then an enterEventDispatch) and any other Thread that might be running in UI code.