Using the TechView UI to Capture System Crash
Information
To configure SCM, Symbian platform provides a TechView-based UI that runs on H4
boards. The TechView UI can be replaced by your own UI, which must use the
configuration API to perform the required tasks.
The following steps guide you through the process of configuring SCM
using the TechView-based UI:
-
Click Tools > Extras and select
coredumpui
application to start the Techview-based
configuration UI on the H4 board.
-
To select the processes or threads to be observed for failure click
Lists > Process or Lists > Thread to view a
list of processes or threads that are running.
-
Select the processes or threads you want to observe for failure and
click Observe.
-
To refresh the list of processes or threads, click
Refresh.
-
To load the plug-ins and change their configuration click Lists
> Plugin to view a list of plug-ins.
-
To load a plug-in, select a plug-in from the list and click
Load.
-
To view and change plug-in configuration, select a plug-in from the
list and click Configure.
-
To configure SCM and to view the core dump server parameters in the
configuration window click Configure > Configure SCM.
The SCM configuration UI provides the following options that are
listed in the table:
Options | Description | Priority
range |
---|
Exception stacks
|
IRQ memory, FIQ stack.
|
0-255
|
Locks
|
Kernel locks.
|
0-255
|
Trace data
|
Contents of the trace buffer.
|
0-255
|
Process code segments
|
Code segments for the crashed process.
|
0-255
|
User thread stack
|
Stacks for the user-side thread(s).
|
0-255
|
Supervisor thread stack
|
Stacks for the supervisor thread(s).
|
0-255
|
User thread registers
|
Registers for the user thread(s).
|
0-255
|
Supervisor thread registers
|
Registers for the supervisor thread(s).
|
0-255
|
Process meta data
|
Meta data for running the processes.
|
0-255
|
Thread meta data
|
Meta data for running threads.
|
0-255
|
Crashed process code Segments
|
Code segments for crashed process.
|
0-255
|
Crashed process user stacks
|
User-side stack for crashed process.
|
0-255
|
Crashed process supervisor stack
|
Supervisor stack for crashed process.
|
0-255
|
Crashed process meta data
|
Meta data for crashed process.
|
0-255
|
Crashed thread meta data
|
Meta data for crashed thread.
|
0-255
|
Variant specific data
|
Variant defined data.
|
0-255
|
Rom info
|
Rom build information.
|
0-255
|
Note: Each Option mentioned in the
preceding table can be given a priority value from 0 (lowest priority) to 255
(highest priority). They are processed by the SCM in order of priority with the
highest priority processed first. A priority value of 0
is
ignored. The space on the flash drive may be limited (especially with multiple
crashes) so the information that is important to be captured in the output must
be given the highest priority.
-
Make necessary changes to the parameter values and click
OK to save the changes, or click Cancel to discard
the changes.
-
To close the application, click Lists > Exit.
After you perform the steps outlined in the preceding list, SCM starts
observing the selected processes and threads for failure and creates the core
dump when a failure is reported. SCM queues the failure events as they occur
and processes them sequentially.
Note: The command-line tool enables you to observe targets
and create the core dump without user interaction. For more information, see
Using the Command-Line Tool.