> I've been down that road...unfortunately the only free malloc/free wrapper
> I tried that actually worked (ccmalloc) totally devastated the system
(i.e.
> lots of time in the cage to fix it) when tested in an environment harsh
> enough to cause the abort's to occur. (Of course, this problem only occurs
> in a heavily loaded "live" environment.)
>
> Anyone have suggestions for other good memory checkers for RedHat
Linux/egcs?
yamd is fairly good, although it does use alot of diskspace with logfiles
...
and is vvery slow
have you tried exporting MALLOC_CHECK_=1 or 2
1 makes the malloc library check for problems, and is more resilliant
2 makes the malloc library kill the program as soon as it notices the
corruption. this should be sooner than the program crashing from the stack
overflow mindyou ..
Thanks,.
Dave
>
> Brent
>
> At 12:51 PM 6/12/2001 -0700, you wrote:
> >Brent Phillips wrote:
> > > Thanks, this helps - what I'm seeing now is copied below. Basically,
pth is
> > > aborting because there are no threads to schedule.
> >
> >Memory corruption somewhere? Maybe try a malloc/free wrapper library.
> >
> >-Archie
> >
>
>__________________________________________________________________________
> >Archie Cobbs * Packet Design *
http://www.packetdesign.com
> >______________________________________________________________________
> >GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
> >User Support Mailing List [EMAIL PROTECTED]
> >Automated List Manager (Majordomo) [EMAIL PROTECTED]
>
>
> ______________________________________________________________________
> GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager (Majordomo) [EMAIL PROTECTED]
>
>
>
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
