i tried Grabserial to measure the startup code of my embedded Linux device. It works somehow but after a while (that means a longer startup code - talking about > 26 s) it stops printing out the messages, but grabserial still is running - i have to hit the [CTRL-C] to retrieve control. I checked the serial port with putty and it's working so it's a problem with grabserial. But i can't think of what it is.
I downloaded and installed with both of the 2 install-variants and it just changed the look-and-feel but stucks at the same point.
Does anyone ever had the same problem ?
Greets
[edit:] i just checked the code, it's nothing special and actually should just break when [CTRL-C] or a timer was set and running out. But the program doesn't even break it just stops printing to console.
[edit2:] i found out, that script is too slow for processing. It seems like it only can output information when something has been sent by the serial line (like an interrupt), but it's like 2 letters transmitted but only 1 is shown. Since the script-processing is slower than booting i can't see everything, only the stuff it managed to show until my device finishes booting. I tried this with a reboot-loop process, so it gets new messages over and over again, and it never stopped printing out.
I still need support for this, does anyone have smart solution before i have to code it by my own?
I've just started using grabserial and I've not reproduced your problem. Current grabserial (1.6.0) does have an option to autostop your program.
-e, --endtime=<secs> End the program after the specified seconds have elapsed.
In case it could help, this is my command line (I've downloaded it from git)
./grabserial -v -d "/dev/ttyUSB1" -b 115200 -w 8 -p N -s 1 -t
来源：https://stackoverflow.com/questions/20518737/grabserial-stops-printing-the-log