Subject:
|
Re: memory leak in string handling
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Mon, 26 Jun 2000 15:12:45 GMT
|
Viewed:
|
1355 times
|
| |
|
|
And the problem is solved. Perhaps my pains can be used for something good
anyway. Perhaps the people who suggested their beautiful strcat-functions
can have (at least the prettiest one) them included in a future release.
And if you're wondering how the problem was solved: My boss came in, took
one look at the code, and said "Hey, what if you do it like this instead?".
It turned out that the strings were never properly deallocated. Some sort of
company secret apparently. :)
Torkel
Torkel Niklasson <torkel.niklasson@telelogic.com> wrote in message
news:FwrC99.BrK@lugnet.com...
> Thank you everyone who helped out. The strcat function works like a charm.
> Unfortunately, the memory leak is still there. I'm beginning to think it
> might be that the strings are never deallocated at all. I'm going to have • to
> check so that the free-function is working properly when I'm using it. Has
> anyone else had any problems with that function?
>
> Torkel
>
> Kekoa Proudfoot <kekoa@pixel.Stanford.EDU> wrote in message
> news:FwGLK4.Esy@lugnet.com...
> > Jamie Obrien <jamien@interworx.com.au> wrote:
> >
> > You can't do this:
> >
> > > char *d2 = *dest;
> >
> > You probably meant char *d2 = dest; like the original author wrote.
> >
> > Here also:
> >
> > > return *dest;
> >
> > You probably meant return dest; like the original author wrote.
> >
> > -Kekoa
>
>
|
|
Message is in Reply To:
 | | Re: memory leak in string handling
|
| Thank you everyone who helped out. The strcat function works like a charm. Unfortunately, the memory leak is still there. I'm beginning to think it might be that the strings are never deallocated at all. I'm going to have to check so that the (...) (24 years ago, 26-Jun-00, to lugnet.robotics.rcx.legos)
|
9 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
