Maybe now that DBG is said to be operational again i will encounter less problems. However i have lost hours(days really) on finding a bug that was just a print statement in a backfill hook function. I also had trouble with printstatements (PutStr) in the library and interface closing code. In code using the pipe functions i learned that PutStr() is safe, and Printf freezes the system. How about the experience of old hands?
Sun, 2012-01-08 22:28#1
debugging print statements cause of trouble.
>> More <PIPE:MyPipethere seemed to be an output of empty lines, but repositioning the cursor in the shell those 'lines' disappeared. After you quitted the program (without quitting Gui4Cli) the same shell command did show what had been written to the pipe. (Quitting Gui4Cli without having emptied the pipe is not possible) Using some kind of print statement in the source code produced output only before the line // ---------- read in a line - length shorter than buffsize for safety This output was directed not to the Gui4Cli console but to another output window. As the goal of the function is to direct output to the latter there may be some interaction i don't understand whch is preventing this. Since i came (today) to this insight, i removed all kind of print statements in the function. To no avail. I have followed advice using (buffered) FOpen instead of Open and still have the same problem. I am out of ideas how to tackle this one. Any help much appreciated (also on how maybe GDB could be used here) Oh yes: at a certain moment playing with MyPipe as well from shell as from the program (you can CLEN (empty) the pipe, set it of or on, the pipe output appeared where it was expected. I was unable to replicate that however.