- Notifications
You must be signed in to change notification settings - Fork81
Dump parsing also optionally trims off CR at the line end#65
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Did the dump come off a Windows machine somehow? |
No, it's running on a beaglebone black running debian. |
fpagliughi commentedApr 18, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
OK. That is weird then. I was curious where it might be coming from. But your addition looks harmless enough. I will try it out and merge when I have a minute. I haven't personally used or touched the code to parse the dump file, but it does look like it could stand to be updated. Seems like it could be simplified using a regex to parse. |
Would you be open to merging this?
I haven't looked intowhy my candump has a \r\n rather than just a \n at the line ending but it does.