I never debugged on beaglebone till 14hrs back. I had been debugging my code on ubuntu desktop and when it worked then I compiled and ran it on beaglebone. So I could only speculate whats happening on beaglebone! Now I debugged on beaglebone... Its producing very weird result! When I put watch on c and I unplug the device then c=255, so I replaced c!=EOF to c!=255 and debugged again, behold, watch on c is c=255 but c!=255 returns true! And the loop never returns! I posted a question regarding it at http://stackoverflow.com/questions/19838702/in-c-how-to-detect-eof-in-arm-architecture . I tried using fstream fin("ttyUSB0", fstream::in) and now when I unplug the device fin>>c never returns and CPU usage is 100% so there should have been an infinite loop inside fin! It might be a bug in the ARM build.
-- *Gowtham* -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
