Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better logging, tracing #15

Open
dd86k opened this issue May 2, 2024 · 0 comments
Open

Better logging, tracing #15

dd86k opened this issue May 2, 2024 · 0 comments
Assignees

Comments

@dd86k
Copy link
Owner

dd86k commented May 2, 2024

Right now, trace logs are only written to stdout, logging is very minimal, and somewhat messy.

Issues:

  1. Alicedbg does not offer logging facilities.
  2. Both the debugger and dumper module lack proper logging formats when it comes to debugging either apps.
  3. Trace builds spam stdout, reducing visibility when debugging.
  4. A little difficult to differentiate between debugger output from debuggee output.

Options:

  1. Provide logging callbacks for Issue 1.
  2. Have tracing output to a alicedbg.log file for Issue 3.

Solutions:

  • Shell: Debug events can be formatted [adbg] event: message.
    • Fixes Issue 2 and 4.
  • Shell: Debugger messages (verbose) can be formatted [adbg] debugger: message.
    • Fixes Issue 2 and 4.
  • Dumper: Can be formatted dumper: message.
    • Fixes Issue 2.
  • Trace output can be written to alicedbg.log and/or alicedump.log.
    • Fixes Issue 3.
@dd86k dd86k self-assigned this May 2, 2024
@dd86k dd86k converted this from a draft issue May 2, 2024
@dd86k dd86k moved this from Considering to Cancelled in alicedbg 0.4 May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Cancelled
Development

No branches or pull requests

1 participant