Changes between Version 2 and Version 3 of Tracing
- Timestamp:
- 2009-07-23T21:50:37Z (15 years ago)
-
Udebug should no longer panic the kernel
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tracing
v2 v3 50 50 * Decoding tables for application protocols are currently very incomplete. Unrecognized calls are not printed at all at the ''protocol'' level, you must display IPC-level messages (`+i`) to see them! 51 51 52 * The re are still bugs, the kernel can panic if the task being traced crashes.52 * The tracer actually kicks in a little while ''before'' the program starts (i.e. at the end of the loader). Thus the first few messages you see concern the loader, rather than the C library startup code. (The loader closes its console connection and answers the RUN call, then it jumps to the entry point of the program). 53 53 54 * The tracer actually kicks in a little while ''before'' the program starts (i.e. at the end of the loader). Thus the first few messages you see concern the loader, rather than the C library startup code. (The loader closes its console connection and answers the RUN call, then it jumps to the entry point of the program).54 * Currently it is not possible to detect which device is hidden behind a file. This means if the application gets the phone and starts talking on it, the tracer has no clue which protocol is being used (such as when Tetris talks directly to the console).
