Debugging information in brew

As the original debugging method, developers can print the debugging information to the output window of the simulator at any position in the application using the dbgprs INTF () in the Help function. The output window of the simulator also displays a large amount of information generated during aee layer running. The meaning of this information is shown in Table 16-1.

Identifier
Description
 
# * GBI
Brew Initialization
 
# * Gex
Exit brew
 
# * GST = <classid>
Send evt_app_start to start the application identified by classid
 
# * GSU = <classid>
Send evt_app_suspend to suspend the application identified by the classid.
 
# * GRE = <classid>
Send evt_app_resume to restore the application identified by classid
 
# * GCL = <classid>
Send evt_app_stop to stop the application identified by classid
 
# * Gxx
Disable all brew applications
 
# * G ** = <errornum>
Brew error code: errornum exception
 
# * G * c = <classid >:< errornum>
The error code generated when creating a classid application or interface is errornum.
 
# * P: ecode: <event>, key: <code>
Key event
 

Table 16-1: Meanings of debugging information in the simulator Output Window

Here are some examples and explanations:

# * GST = 16809984 start a BREW application whose classid is 16809984

# * P: ecode: 101, key: e035 the user presses the "select" key and generates the avk_select evt_key_press event accordingly.

# * P: ecode: 100, key: e035 the user presses the "select" key and generates an avk_select evt_key event.

# * P: ecode: 102, key: e035 the user presses the "select" key and generates an avk_select evt_key_release event.

# * GSU = 16809984 a BREW application of classid16809984 is suspended on a mobile phone or Simulator

# * GCL = 16809984 because the app with the classid of 16809984 does not handle the evt_app_suspend event, the app is disabled by the mobile phone or simulator.

# * G * c = 101402c: 3 The eclassnotsupport error is returned when you create an application or interface whose classid is 0x101402c.

If developers can clearly understand the meaning of the information, it will be of great help for application debugging.

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/wireless_com/archive/2010/11/30/6045553.aspx