글
Technical Article/펌 2005. 7. 18. 16:54[MB] Brew Debug Sequence Information
Debug Sequence Information
--------------------------------------------------------------------------------
Information on Debug Sequences:
Please note that all the Debug key sequences noted below are the default key sequences. These key sequences may be modified by the OEM.
###0: Turn Debugging off
This debug key sequence resets/toggles off all debug states.
###1: Memory Validation
On every heap access, BREW walks the heap to determine if the pointer is in valid range and will not over-write/over-read a heap node. An exception will be thrown if the heap access will cause corruption of a heap node.
###2: Net Debug Tool
The Net Debug Tool can be used to view the device's network (socket and PPP) states while your application is running. When the Net Debug Tool is turned on, a box will appear in the right hand corner and will display a series of codes that can be used to determine the state of your application's data call. The codes vary per BREW version and are shown below.
Network State Codes:
BREW 1.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
' ' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'd' PPP Opening
'D' PPP Open
'-' PPP Closing
'O' PPP Closed
BREW 1.1:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'd' PPP Opening
'D' PPP Open
'z' PPP Closing
'Z' PPP Closed
BREW 2.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'b' Socket Bind
'B' Socket Bound
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'^' PPP Opening
'=' PPP Open
'v' PPP Closing
'#' PPP Closed
'<' PPP Sleeping
'~' PPP Asleep
'>' PPP Waking
###3: Largest Available Heap Block
Displays the maximum size block that can be allocated on the heap in the upper left corner of the screen.
###4: Debug Privileges
This debug sequence is not yet implemented.
###5: Debug Malloc – throws exception on MALLOC failure
Throws an exception on malloc failure.
###6: Debug Null – Every Nth MALLOC is failed
When this debug sequence is turned on, every Nth MALLOC will fail, even if RAM is available. Currently, N is set to 100.
###7: Sync/Async DBGPRINTF
This debug sequence toggles between two modes: synchronous DBGPRINTF and asynchronous DBFPRINTF. In synchronous DBGPRINTF mode, BREW waits for certain duration before returning from a DBGPRINTF statement in order to allow time for the DBGPRINTF message to be sent on the serial port. In the default, asynchronous mode, the DBGPRINTF returns immediately.
###8: Debug Dump Modules
This debug sequence is not yet implemented.
###9: Debug Dump Heap
Every time this sequence is pressed, heap and resource usage information is dumped on the emulator debug window or onto the Serial port.
The heap info consists of the number of bytes, the system that allocates it, an internally used index, the file name and line number, and whether the memory is locked (L) or unlocked(U).
Additional information is displayed on Allocated and Free RAM, and resource usage.
__________________
Max
BREW Support
mohlendo
View Public Profile
Send a private message to mohlendo
Visit mohlendo's homepage!
Find all posts by mohlendo
Add mohlendo to Your Buddy List
#2 03-19-2004, 03:09 AM
tyndal
Registered User Join Date: Dec 2002
Posts: 926
on the vx6000, the debug sequence is
**********
instead of
###
please post any other known debug sequences here.
-Tyndal
tyndal
View Public Profile
Send a private message to tyndal
Find all posts by tyndal
Add tyndal to Your Buddy List
#3 07-23-2004, 09:18 AM
KIRAN
Registered User Join Date: Jun 2004
Posts: 5
Thanks
--------------------------------------------------------------------------------
Many thanks for providing vital information regarding debug key sequences. This is indeed very much useful to developers.
Thanks once again,
Kiran.
KIRAN
View Public Profile
Send a private message to KIRAN
Send email to KIRAN
Find all posts by KIRAN
Add KIRAN to Your Buddy List
#4 07-28-2004, 06:08 AM
accolade
Registered User Join Date: Apr 2004
Posts: 153
###6: Debug Null – Every Nth MALLOC is failed
When this debug sequence is turned on, every Nth MALLOC will fail, even if RAM is available. Currently, N is set to 100.
How do we change N to 2 or 3 or 1 ?
Thanks,
Quote:
Originally Posted by mohlendo
Information on Debug Sequences:
Please note that all the Debug key sequences noted below are the default key sequences. These key sequences may be modified by the OEM.
###0: Turn Debugging off
This debug key sequence resets/toggles off all debug states.
###1: Memory Validation
On every heap access, BREW walks the heap to determine if the pointer is in valid range and will not over-write/over-read a heap node. An exception will be thrown if the heap access will cause corruption of a heap node.
###2: Net Debug Tool
The Net Debug Tool can be used to view the device's network (socket and PPP) states while your application is running. When the Net Debug Tool is turned on, a box will appear in the right hand corner and will display a series of codes that can be used to determine the state of your application's data call. The codes vary per BREW version and are shown below.
Network State Codes:
BREW 1.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
' ' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'd' PPP Opening
'D' PPP Open
'-' PPP Closing
'O' PPP Closed
BREW 1.1:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'd' PPP Opening
'D' PPP Open
'z' PPP Closing
'Z' PPP Closed
BREW 2.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'b' Socket Bind
'B' Socket Bound
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'^' PPP Opening
'=' PPP Open
'v' PPP Closing
'#' PPP Closed
'<' PPP Sleeping
'~' PPP Asleep
'>' PPP Waking
###3: Largest Available Heap Block
Displays the maximum size block that can be allocated on the heap in the upper left corner of the screen.
###4: Debug Privileges
This debug sequence is not yet implemented.
###5: Debug Malloc – throws exception on MALLOC failure
Throws an exception on malloc failure.
###6: Debug Null – Every Nth MALLOC is failed
When this debug sequence is turned on, every Nth MALLOC will fail, even if RAM is available. Currently, N is set to 100.
###7: Sync/Async DBGPRINTF
This debug sequence toggles between two modes: synchronous DBGPRINTF and asynchronous DBFPRINTF. In synchronous DBGPRINTF mode, BREW waits for certain duration before returning from a DBGPRINTF statement in order to allow time for the DBGPRINTF message to be sent on the serial port. In the default, asynchronous mode, the DBGPRINTF returns immediately.
###8: Debug Dump Modules
This debug sequence is not yet implemented.
###9: Debug Dump Heap
Every time this sequence is pressed, heap and resource usage information is dumped on the emulator debug window or onto the Serial port.
The heap info consists of the number of bytes, the system that allocates it, an internally used index, the file name and line number, and whether the memory is locked (L) or unlocked(U).
Additional information is displayed on Allocated and Free RAM, and resource usage.
accolade
View Public Profile
Send a private message to accolade
Find all posts by accolade
Add accolade to Your Buddy List
#5 10-12-2004, 10:16 PM
ericF
Registered User Join Date: Apr 2004
Posts: 79
in fact, my handset is taking * instead of #.
ericF
View Public Profile
Send a private message to ericF
Find all posts by ericF
Add ericF to Your Buddy List
#6 10-12-2004, 10:40 PM
nparrish
Super Moderator Join Date: Apr 2004
Posts: 514
Some handsets deviate from the standard ###X sequence.
The LG VX6000/4500/4600 line, for example use **********X as the sequence.
The LG VX7000/8000, on the otherhand, use #######X.
This is typically documented on the known issues page for each device.
__________________
Nathan
BREW Support
nparrish
View Public Profile
Send a private message to nparrish
Send email to nparrish
Find all posts by nparrish
Add nparrish to Your Buddy List
#7 06-23-2005, 06:52 PM
pumasilk
Registered User Join Date: Jun 2005
Posts: 4
Debug sequence for my vx8000 is *******X ( '*' 7 times )
pumasilk
View Public Profile
Send a private message to pumasilk
Send email to pumasilk
Find all posts by pumasilk
Add pumasilk to Your Buddy List
#8 06-23-2005, 09:27 PM
Skavenger
Registered User Join Date: May 2004
Posts: 182
Is there anyway we can get this information put in the DDS's?
__________________
- Skavenger
출처 : 퀄컴 개발자 포럼
--------------------------------------------------------------------------------
Information on Debug Sequences:
Please note that all the Debug key sequences noted below are the default key sequences. These key sequences may be modified by the OEM.
###0: Turn Debugging off
This debug key sequence resets/toggles off all debug states.
###1: Memory Validation
On every heap access, BREW walks the heap to determine if the pointer is in valid range and will not over-write/over-read a heap node. An exception will be thrown if the heap access will cause corruption of a heap node.
###2: Net Debug Tool
The Net Debug Tool can be used to view the device's network (socket and PPP) states while your application is running. When the Net Debug Tool is turned on, a box will appear in the right hand corner and will display a series of codes that can be used to determine the state of your application's data call. The codes vary per BREW version and are shown below.
Network State Codes:
BREW 1.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
' ' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'd' PPP Opening
'D' PPP Open
'-' PPP Closing
'O' PPP Closed
BREW 1.1:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'd' PPP Opening
'D' PPP Open
'z' PPP Closing
'Z' PPP Closed
BREW 2.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'b' Socket Bind
'B' Socket Bound
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'^' PPP Opening
'=' PPP Open
'v' PPP Closing
'#' PPP Closed
'<' PPP Sleeping
'~' PPP Asleep
'>' PPP Waking
###3: Largest Available Heap Block
Displays the maximum size block that can be allocated on the heap in the upper left corner of the screen.
###4: Debug Privileges
This debug sequence is not yet implemented.
###5: Debug Malloc – throws exception on MALLOC failure
Throws an exception on malloc failure.
###6: Debug Null – Every Nth MALLOC is failed
When this debug sequence is turned on, every Nth MALLOC will fail, even if RAM is available. Currently, N is set to 100.
###7: Sync/Async DBGPRINTF
This debug sequence toggles between two modes: synchronous DBGPRINTF and asynchronous DBFPRINTF. In synchronous DBGPRINTF mode, BREW waits for certain duration before returning from a DBGPRINTF statement in order to allow time for the DBGPRINTF message to be sent on the serial port. In the default, asynchronous mode, the DBGPRINTF returns immediately.
###8: Debug Dump Modules
This debug sequence is not yet implemented.
###9: Debug Dump Heap
Every time this sequence is pressed, heap and resource usage information is dumped on the emulator debug window or onto the Serial port.
The heap info consists of the number of bytes, the system that allocates it, an internally used index, the file name and line number, and whether the memory is locked (L) or unlocked(U).
Additional information is displayed on Allocated and Free RAM, and resource usage.
__________________
Max
BREW Support
mohlendo
View Public Profile
Send a private message to mohlendo
Visit mohlendo's homepage!
Find all posts by mohlendo
Add mohlendo to Your Buddy List
#2 03-19-2004, 03:09 AM
tyndal
Registered User Join Date: Dec 2002
Posts: 926
on the vx6000, the debug sequence is
**********
instead of
###
please post any other known debug sequences here.
-Tyndal
tyndal
View Public Profile
Send a private message to tyndal
Find all posts by tyndal
Add tyndal to Your Buddy List
#3 07-23-2004, 09:18 AM
KIRAN
Registered User Join Date: Jun 2004
Posts: 5
Thanks
--------------------------------------------------------------------------------
Many thanks for providing vital information regarding debug key sequences. This is indeed very much useful to developers.
Thanks once again,
Kiran.
KIRAN
View Public Profile
Send a private message to KIRAN
Send email to KIRAN
Find all posts by KIRAN
Add KIRAN to Your Buddy List
#4 07-28-2004, 06:08 AM
accolade
Registered User Join Date: Apr 2004
Posts: 153
###6: Debug Null – Every Nth MALLOC is failed
When this debug sequence is turned on, every Nth MALLOC will fail, even if RAM is available. Currently, N is set to 100.
How do we change N to 2 or 3 or 1 ?
Thanks,
Quote:
Originally Posted by mohlendo
Information on Debug Sequences:
Please note that all the Debug key sequences noted below are the default key sequences. These key sequences may be modified by the OEM.
###0: Turn Debugging off
This debug key sequence resets/toggles off all debug states.
###1: Memory Validation
On every heap access, BREW walks the heap to determine if the pointer is in valid range and will not over-write/over-read a heap node. An exception will be thrown if the heap access will cause corruption of a heap node.
###2: Net Debug Tool
The Net Debug Tool can be used to view the device's network (socket and PPP) states while your application is running. When the Net Debug Tool is turned on, a box will appear in the right hand corner and will display a series of codes that can be used to determine the state of your application's data call. The codes vary per BREW version and are shown below.
Network State Codes:
BREW 1.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
' ' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'd' PPP Opening
'D' PPP Open
'-' PPP Closing
'O' PPP Closed
BREW 1.1:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'd' PPP Opening
'D' PPP Open
'z' PPP Closing
'Z' PPP Closed
BREW 2.0:
'c' Socket Connecting
'C' Socket Connected
'x' Socket Closing
'X' Socket Closed
'I' Socket Idle
'b' Socket Bind
'B' Socket Bound
'R' Socket Read
'W' Socket Write
'r' Socket RecvFrom
'w' Socket SendTo
'^' PPP Opening
'=' PPP Open
'v' PPP Closing
'#' PPP Closed
'<' PPP Sleeping
'~' PPP Asleep
'>' PPP Waking
###3: Largest Available Heap Block
Displays the maximum size block that can be allocated on the heap in the upper left corner of the screen.
###4: Debug Privileges
This debug sequence is not yet implemented.
###5: Debug Malloc – throws exception on MALLOC failure
Throws an exception on malloc failure.
###6: Debug Null – Every Nth MALLOC is failed
When this debug sequence is turned on, every Nth MALLOC will fail, even if RAM is available. Currently, N is set to 100.
###7: Sync/Async DBGPRINTF
This debug sequence toggles between two modes: synchronous DBGPRINTF and asynchronous DBFPRINTF. In synchronous DBGPRINTF mode, BREW waits for certain duration before returning from a DBGPRINTF statement in order to allow time for the DBGPRINTF message to be sent on the serial port. In the default, asynchronous mode, the DBGPRINTF returns immediately.
###8: Debug Dump Modules
This debug sequence is not yet implemented.
###9: Debug Dump Heap
Every time this sequence is pressed, heap and resource usage information is dumped on the emulator debug window or onto the Serial port.
The heap info consists of the number of bytes, the system that allocates it, an internally used index, the file name and line number, and whether the memory is locked (L) or unlocked(U).
Additional information is displayed on Allocated and Free RAM, and resource usage.
accolade
View Public Profile
Send a private message to accolade
Find all posts by accolade
Add accolade to Your Buddy List
#5 10-12-2004, 10:16 PM
ericF
Registered User Join Date: Apr 2004
Posts: 79
in fact, my handset is taking * instead of #.
ericF
View Public Profile
Send a private message to ericF
Find all posts by ericF
Add ericF to Your Buddy List
#6 10-12-2004, 10:40 PM
nparrish
Super Moderator Join Date: Apr 2004
Posts: 514
Some handsets deviate from the standard ###X sequence.
The LG VX6000/4500/4600 line, for example use **********X as the sequence.
The LG VX7000/8000, on the otherhand, use #######X.
This is typically documented on the known issues page for each device.
__________________
Nathan
BREW Support
nparrish
View Public Profile
Send a private message to nparrish
Send email to nparrish
Find all posts by nparrish
Add nparrish to Your Buddy List
#7 06-23-2005, 06:52 PM
pumasilk
Registered User Join Date: Jun 2005
Posts: 4
Debug sequence for my vx8000 is *******X ( '*' 7 times )
pumasilk
View Public Profile
Send a private message to pumasilk
Send email to pumasilk
Find all posts by pumasilk
Add pumasilk to Your Buddy List
#8 06-23-2005, 09:27 PM
Skavenger
Registered User Join Date: May 2004
Posts: 182
Is there anyway we can get this information put in the DDS's?
__________________
- Skavenger
출처 : 퀄컴 개발자 포럼
RECENT COMMENT