--- 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. ~Kender ===== -----BEGIN GEEK CODE BLOCK----- Version 3.1 GCS/L/C/O d-(+) s++:+ a-- C+++$>++++ UBLS++++$ P+++(--)$ L++>+++ E--- W+>++$ N !o K? w(--) !O M- !V PS+ PE(++) Y+ PGP->+ t- 5 X+() R(+) tv+@ b++(+++) !DI+++ D G(-) e>+++$ h---() r+++ y+++ ------END GEEK CODE BLOCK------ __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
