roscpp: ros::Time::now() not working correctly on windows (ros ticket #3790)

[tfoote]

Environment
Windows 7 Pro 32bit on Intel E2180 processor

Code
ros::init(argc, argv, "test");
while(1)
{
ros::Time t= ros::Time::now();
Sleep(10);
printf("%ld,%ld\n",t.sec, t.nsec);
}
Output
1323720814,945105920
1323720814,955104384
1323720815,965104384
1323720815,975104384
1323720815,985106432
1323720815,995106432
1323720815,6104896
1323720815,16103872
1323720815,27103360
1323720815,37104384
Note the t.sec field does not increase at the same time as t.nsec cycle over 1e9 to 0

I trace down the problem to the code
void ros_walltime(uint32_t& sec, uint32_t& nsec) as in
http://www.ros.org/doc/api/rostime/html/time_8cpp_source.html#l00095

A standalone (without any roslib)win32 console application using the same code snippet in ros_walltime to obtain the (sec,nsec) further suggests this code is the source of problem. (code attached)

trac data:

• Owner: straszheim
• Reporter: tingfan
• Reported at: Mon Dec 12 12:28:07 2011
• URL: https://code.ros.org/trac/ros/ticket/3790

[tfoote]

[tingfan] Reformatting of [ticket:3790 tingfan]:

Environment

Windows 7 Pro 32bit on Intel E2180 processor

Code and Output
{{{

ros::init(argc, argv, "test");
while(1)
{
    ros::Time t= ros::Time::now();
    Sleep(10);
    printf("%ld,%ld\n",t.sec, t.nsec);
}

Output
1323720814,945105920
1323720814,955104384
1323720815,965104384
1323720815,975104384
1323720815,985106432
1323720815,995106432
1323720815,6104896
1323720815,16103872
1323720815,27103360
1323720815,37104384
Note the t.sec field does not increase at the same time as t.nsec cycle over 1e9 to 0
}}}

I trace down the problem to the code
void ros_walltime(uint32_t& sec, uint32_t& nsec) as in
http://www.ros.org/doc/api/rostime/html/time_8cpp_source.html#l00095

A standalone (without any roslib)win32 console application using the same code snippet in ros_walltime to obtain the (sec,nsec) further suggests this code is the source of problem. (code attached)

[stonier]

We tried reproducing this here without success.

I put a couple of commits into rostime quite some time ago - perhaps these fixed the situation, or it's a problem only on certain machines/platforms.

I'd recommend closing this and re-opening it if necessary (i.e. someone else manages to reproduce the problem).

[dirk-thomas]

Thank you.