Ticket #30 (closed Tasks: fixed)
Implement debugging data capture
| Reported by: | octo | Owned by: | octo |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.4 |
| Component: | LogicMail | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Currently there is no way to capture useful debugging data from the device when there is an error caused by a bug or server incompatibility issue.
This task is to implement some form of low-overhead logging system, such as MicroLog or Jadabs-CLDC. In addition to logging program activities, it would also have to potentially capture a packet trace when the MailClientHandler catches an exception. Packet trace capture should be off by default, but the ability to turn it on would be immensely valuable for debugging.
Retrieval of this data is more complex, but one idea is to cheat and insert it into something like the ToDo list via the J2ME PIM API. Another idea is to dump it to standard output, but that would only be useful if LogicMail were running inside the simulator.
Change History
comment:2 Changed 5 years ago by octo
- Status changed from assigned to closed
- Resolution set to fixed
The basic feature has been implemented, to a reasonable extent. The whole application is not instrumented, but the protocol/network portions are. These are the portions whose bugs are most difficult to reproduce by anyone other than the end user. Additional logging will be added on an as-needed basis.
Current plan involves using the built-in EventLogger API. Low-level network traffic will be logged at the DEBUG_INFO level, exceptions will be logged at WARNING or ERROR, and other activities will be logged at the INFORMATION level.