-
Notifications
You must be signed in to change notification settings - Fork 23
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
missing \n on (some) CPLDC messages? #20
Comments
All CPDLC downlink messages with a "FREE TEXT" label are mapped to a dumpvdl2 prints decoded text output to files using Hence, I can't come up with any scenario which would cause these newlines to be omitted. I've also grepped all my log files collected this and last year and have found no such occurrences. Are you logging messages to files? Does the output look the same in the file or only in multitail? Maybe the output got corrupted by multitail or the terminal? If the problem is real, I need a raw message log produced either with |
Thanks for the code walkout, it's helpful.
Indeed both occurrences happened with dumpvdl2 running within multitail, and both from the same terminal software (one over SSH, the other local), and I've seen it only once as reported above. One thing that should rule out terminal corruption though is that as you can see from the report, the "corrupted" output is visible in multitail backlog: that's really what told me I hadn't a cross-eyed moment :). Maybe it was indeed a multitail bug then and if you've never seen this in your year-long logfiles I think it's safe to ignore this report, so I'm closing it. Sorry for the noise. |
Purely FYI it just happened again as I was randomly taking a look at the output (still piped through multitail, running with
|
and one more, maybe related, datapoint: running
No This grep response (and end of output) can typically be caused by null bytes in the output stream: I'm not sure dumpvdl2 is supposed to put out any in FWIW a null byte that "eats" the expected "\n" could certainly cause the situation reported in the first post. HTH |
Hi,
(While testing a new antenna) I noticed the following output from dumpvdl2 (simultaneously on two separate machines running from different dongles - so probably not a fluke):
(This is a copy-paste from multitail backlog, hence the minor garbage at beginning of lines.)
The FREE TEXT message is apparently printed without a terminating newline, resulting in the header of the next frame being appended to the message.
I tried looking into the code to fix this but eventually got lost in all the levels of print/formatting indirections and gave up. I hope this provides enough info to locate the problem though. I think this bug lies in libacars, hence opening the issue here.
HTH
The text was updated successfully, but these errors were encountered: