ok, I'll verify that, it sounds correct. the reason for those \r's is the original code is for copying large files with some extra things which arent in say cp or dd, where I had a progress indicator, say every 128 MB or user defined amount copied, it would echo the next progress, where it would use
printf( "\r%lluMB ", total_bytes_copied >> 20 ) ; to progress the indicator, and then on successful completion, it would echo "\r \r", with enough spaces to erase the progress indicator and be ready for any further text, to avoid an unused line of text. I hadnt thought that it would complete the loop in the pared down example and then erase all the debug output! so it must loop twice, then exit, then erase all the debug echoes! can you advise which URL for reporting an unrelated problem, which is that Linux Mint seems to use full precision nanonsecond timestamps, but when I use utimensat() to replicate timestamps it only replicates to a 0.01 second precision. This problem emerged when I then wrote code to verify timestamps the same and found they werent. on scrutinising I found that say 987654321 nanoseconds was getting set as 980000000 nanoseconds. so at the moment I am having to verify nanonseconds/10000000 are the same. I think that isnt a gcc bug, but not sure which project it relates to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2119376 Title: program starts with printf("a");fflush(stdout);yet doesnt echo anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/2119376/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
