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

store logs somewhere + always log #13

Open
fenugrec opened this issue May 31, 2021 · 3 comments
Open

store logs somewhere + always log #13

fenugrec opened this issue May 31, 2021 · 3 comments

Comments

@fenugrec
Copy link
Owner

(must be fixed via freediag).

I've had enough of "it gave an error, I don't remember what it was, it broke everything" reports

@Pytrex
Copy link
Contributor

Pytrex commented Dec 29, 2021

I'd definitely support always logging! On top of this, I'd recommend having it log both the bytes sent/received AND the actual error being reported. I've had to resort to sniffing the comms using wireshark just to figure out why Nisprog gets mad about something haha

@fenugrec
Copy link
Owner Author

I've had to resort to sniffing the comms using wireshark

Could you not just "debug L1 0x8c" ? or maybe l2 0x8c would even suffice, with less noise...

@Pytrex
Copy link
Contributor

Pytrex commented Dec 30, 2021

Could you not just "debug L1 0x8c" ? or maybe l2 0x8c would even suffice, with less noise...

Maybeee? I really haven't messed with debug stuff. The one time I did two years back it just spammed me with data and wouldn't really let me do much about it lol But I could definitely mess with the debug stuff a bit and see if maybe things have changed since then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants