ckim@esunix.UUCP (Cheol Kim) (05/25/89)
'malloc' VS 'calloc' ------------------- The problem with using malloc is just that, memory is not freed when exiting from the program. However, it would be interesting to using 'calloc' instead of 'malloc'. Memory allocated by using 'calloc' is supposed to be freed upon exit in a regular UNIX system. Hope that it is the same with vxWorks. Loader problem -------------- We have been loading routines repeatedly in mod-compile-debug cycle. Our programs are quite substantial and they use quite a bit of memory. I was hoping that there is a switch to load routines after freeing memory allocated under the same names. For example, if one loads 'foo' thrice, there will be three routines named 'foo'. Implicitly, the most recent is executed. We rarely use old versions. Thus, we feel that there could be more intelligent loader. 'fseek' problem --------------- A while ago, we've came across a problem with 'fseek'. It works nicely once and then it fouls the file pointer badly. Therefore, we had to write our own using 'getch()'. Barf!!! Bug report ---------- I have never yet seen a list of bugs reported and contained in the current vxWorks software. Such monster is so much more important than marketing brochure to current users of vxWorks. cheol