My apologies in advance if I'm asking a stupid question.
I did a simple count of malloc's and free's occurring in TinyScheme 1.38 and noticed at the final cleanup there are many free's that had no (apparent to me at least) malloc's.
According to GNU mtrace under Linux, there is no memory leak, but I'm worried once I try to put this on some of my simpler embedded systems, this free-without-malloc issue will cause crashes.
Does anyone have experiences (or explanations) on why this is taking place?
Best regards,
-joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would help to have additional information to know whether you have actually found a problem or not. Check out a copy of TinyScheme from CVS (or at least get version 1.39) and see if you still the same problem. If you do, a list of the specific malloc's in question would be a big help. Your list should include the version number of TinyScheme you are using (if you use CVS, the date you did your check out), along with the line number references to the malloc's.
Once that information is available, this issue can be examined in more detail.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My apologies in advance if I'm asking a stupid question.
I did a simple count of malloc's and free's occurring in TinyScheme 1.38 and noticed at the final cleanup there are many free's that had no (apparent to me at least) malloc's.
According to GNU mtrace under Linux, there is no memory leak, but I'm worried once I try to put this on some of my simpler embedded systems, this free-without-malloc issue will cause crashes.
Does anyone have experiences (or explanations) on why this is taking place?
Best regards,
-joe
It would help to have additional information to know whether you have actually found a problem or not. Check out a copy of TinyScheme from CVS (or at least get version 1.39) and see if you still the same problem. If you do, a list of the specific malloc's in question would be a big help. Your list should include the version number of TinyScheme you are using (if you use CVS, the date you did your check out), along with the line number references to the malloc's.
Once that information is available, this issue can be examined in more detail.