[planetf1]

Hi,
I'm a developer, but not (yet) on Symbian... so forgive the newbie question.

If I have a handset "hang" (ie battery out job) is there any way to retrieve any failure information / core dump etc from the phone to discover what apps/threads were running at the time, stack traces etc to help indentify the fault - at least in terms of area, or even help to understand the scenario building up to the hang. (On an unmodified device in the field, as opposed to emulator etc)

I've done this before on various *nix systems, windows etc, but not sure if it's possible / where to start on S60.

Thanks

[planetf1]

Anyone?

I'm seeing regular hangs on my N96, even after a full hard reset. It could be the base firmware/apps, or 3rd party , and it's difficult to know what causes it.

Under *nix, windows I could examine a system dump to figure out what module/thread etc may have caused the issue. At least enough to have a clue as to what to change, avoid doing, or to provide more info in a bug report.

I've not looked into comparable iPhone/Android environments -- obviously phones are somewhat constrained in capabilities, although it's far less than it used to be.

Now whilst some of this could be done under emulation the issue may well be device specific. And no formal test will ever find all the issues that real customer usage "in the wild" hits.

So have I missed some capability? Or is this not possible

If I was choosing a platform to develop on this would definately be a significant *technical* factor in that choice.

[ltomuta]

Unfortunately currently there are no tools available for you to collect and analyse system crash logs.