----- Original Message ----- From: "Chad Simmons" <[EMAIL PROTECTED]> To: "Mike Barton" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Wednesday, May 15, 2002 7:46 PM Subject: Re: memory leaks
> > --- Mike Barton <[EMAIL PROTECTED]> wrote: > > > > I think what Edwin was referring to was fixing the actual memory leaks > > > > (especially if there are "several memory leaks i know are in there", not > > > > redesigning anything. > > > Ah, well when the OP said that he was trying to debug the memory leaks but > > > the mud wasn't dropping core anymore because of the pthreads problem I > > > assumed that in order for him to go about fixing the leak issues he wanted > > > to have his core files back. Thus my suggestion for redesigning his system > > > > How's gdb going to be a huge help with memory leaks anyway? > > And if you're getting a core file, I think a memory leak is the least of your > > > > worries. > > Or should I assume that people are going to call any bug a memory leak? > > That's what my assumtion was. Most "mud coders" don't really know what a memory > leak is, (often the assumtion is anything that crashes the mud is a memory > leak). So I guessed when he started talking about core files that he was not > actually talking about memory leaks, and thus tried to help with the core file > issue. If he actually has problems with memory leaking then you are right, gdb > and core files won't really help much. > heh, i know what memleaks are, i also know cores and gdb are useless to find them. My biggest problem atm is that i'm the only coder that actually has more than 2 months programming experience (6 yrs by now, on various codebases, and non-mud things), and have an idea when i've got a memleak problem.... the whole gdb thing was a second question only ;) i can live without having cores and stuff, it'll be annoying, but i can live with it. That which i do have lots of problems with is memory leaks, i assume there are several dozens of them in the code, some more frequently used than others, but still way too many (1's too much already ;) )
