View Single Post
Old 07-14-2012, 07:32 PM   #180
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
One thing about tiny little code with no error messages is that you get to rely on the general all-purpose error message called "segfault".

And then there are those darned built-in libraries that spoil the party by injecting their own error messages before aborting.

Of course, in "real" code (especially all the motion-control / robotics / factory automation stuff I did over the years), you need to recover gracefully from just about anything that can happen, logging it silently while not annoying the machine operator, and self-calibrating WHILE in operation. You cannot shut down operations just because the machine is failing, if your software can compensate for the progressive failure. But you also cannot just hit the reset button to restart after a large part of your machine goes through a brick wall and out into the parking lot because of a software glitch.

Now, the reason I brought this up, is that I am getting segfaults with your latest code. PEBKAC errors no doubt.

Last edited by geekmaster; 07-14-2012 at 07:42 PM.
geekmaster is offline   Reply With Quote