From mboxrd@z Thu Jan  1 00:00:00 1970
From: atharaken@my-deja.com
To: help-gcc@gnu.org
Subject: Re: Segmentation Fault: new char[12]
Date: Wed, 08 Dec 1999 07:21:00 -0000
Message-id: <82ls9f$8il$1@nnrp1.deja.com>
References: <82jp3a$pal$1@nnrp1.deja.com> <82kesh$994$1@nnrp1.deja.com>
X-SW-Source: 1999-12/msg00118.html

Any free tools to detect memory leaks!!! Purify and Insure both cost a
lot. Any others!

In article < 82kesh$994$1@nnrp1.deja.com >,
  hwidjaja@my-deja.com wrote:
> I didn't see problem at your code..
> you mentioned that i gives a segm. fault when large number of users
> are accessing it ...
> I suspect that there is memory leaks in your code. Then you run out of
> memory...
> my suggestion is to check it,
>  you can use 'top -U<username>' or 'ps'.
>
> hwidjaja
> In article < 82jp3a$pal$1@nnrp1.deja.com >,
>   atharaken@my-deja.com wrote:
> > This is a snippet of some code I am using. I get a Segmentation
Fault
> > in _smalloc (malloc). It works sometimes and when a large number of
> > users are accessing it gives a segmentation fault.
> >
> > It happens at the line:
> >
> > _string = new char [_capacity];
> >
> > I call this using _Init(12);
> > This is a protected class.
> >
> > /* BEGIN CODE HERE */
> >
> > bool MyClass::_Init (long size)
> > {
> >     _capacity = size;
> >     _string = new char [_capacity]; //Get Segmentation Fault at
> _smalloc
> >     if (!_string) {
> >         _capacity = _size = 0L;
> >         return false;
> >     }
> >     _size = 0;
> >     _string[0] = '\0';
> >     return true;
> > }
> >
> > /*END CODE HERE */
> >
> > Machine: i386
> > OS: Solaris 7
> > GCC 2.95 (Release)
> >
> > Any help is appreciated
> >
> > Thanks
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> >
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>


Sent via Deja.com http://www.deja.com/
Before you buy.

From mboxrd@z Thu Jan  1 00:00:00 1970
From: atharaken@my-deja.com
To: help-gcc@gnu.org
Subject: Re: Segmentation Fault: new char[12]
Date: Fri, 31 Dec 1999 22:24:00 -0000
Message-ID: <82ls9f$8il$1@nnrp1.deja.com>
References: <82jp3a$pal$1@nnrp1.deja.com> <82kesh$994$1@nnrp1.deja.com>
X-SW-Source: 1999-12n/msg00118.html
Message-ID: <19991231222400.9jUATemWiwfUKiIneO8lbvqNDrsmgFZLjJlbYKsbqMk@z>

Any free tools to detect memory leaks!!! Purify and Insure both cost a
lot. Any others!

In article < 82kesh$994$1@nnrp1.deja.com >,
  hwidjaja@my-deja.com wrote:
> I didn't see problem at your code..
> you mentioned that i gives a segm. fault when large number of users
> are accessing it ...
> I suspect that there is memory leaks in your code. Then you run out of
> memory...
> my suggestion is to check it,
>  you can use 'top -U<username>' or 'ps'.
>
> hwidjaja
> In article < 82jp3a$pal$1@nnrp1.deja.com >,
>   atharaken@my-deja.com wrote:
> > This is a snippet of some code I am using. I get a Segmentation
Fault
> > in _smalloc (malloc). It works sometimes and when a large number of
> > users are accessing it gives a segmentation fault.
> >
> > It happens at the line:
> >
> > _string = new char [_capacity];
> >
> > I call this using _Init(12);
> > This is a protected class.
> >
> > /* BEGIN CODE HERE */
> >
> > bool MyClass::_Init (long size)
> > {
> >     _capacity = size;
> >     _string = new char [_capacity]; //Get Segmentation Fault at
> _smalloc
> >     if (!_string) {
> >         _capacity = _size = 0L;
> >         return false;
> >     }
> >     _size = 0;
> >     _string[0] = '\0';
> >     return true;
> > }
> >
> > /*END CODE HERE */
> >
> > Machine: i386
> > OS: Solaris 7
> > GCC 2.95 (Release)
> >
> > Any help is appreciated
> >
> > Thanks
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> >
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>


Sent via Deja.com http://www.deja.com/
Before you buy.