Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Oleg Derevenetz
On Wed, 18 Aug 1999, Ilia Chipitsine wrote: > > > > Why i think this is bug? Because any user can hung FreeBSD, settings in > > > > /etc/login.conf can't help. > > > > >Are you sure about that? Setting datasize limits will prevent > > >malloc() from doing what you're trying to make it do. Are

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Oleg Derevenetz
On Wed, 18 Aug 1999, Ilia Chipitsine wrote: > > > > Why i think this is bug? Because any user can hung FreeBSD, settings in > > > > /etc/login.conf can't help. > > > > >Are you sure about that? Setting datasize limits will prevent > > >malloc() from doing what you're trying to make it do. Ar

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Ilia Chipitsine
On Tue, 17 Aug 1999, Alec Kalinin wrote: > > > Why i think this is bug? Because any user can hung FreeBSD, settings in > > > /etc/login.conf can't help. > > >Are you sure about that? Setting datasize limits will prevent > >malloc() from doing what you're trying to make it do. Are you > >sure yo

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Ilia Chipitsine
On Tue, 17 Aug 1999, Alec Kalinin wrote: > > > Why i think this is bug? Because any user can hung FreeBSD, settings in > > > /etc/login.conf can't help. > > >Are you sure about that? Setting datasize limits will prevent > >malloc() from doing what you're trying to make it do. Are you > >sure y

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Mark Newton
Biju Susmer wrote: > > Well, yeah, that's becuase you're running it out of swap by trying to > > allocate a gigabyte of memory. > > but this is done in steps of 1MB. Once it reaches out of memory, malloc > should return NULL. Since there is no checking for NULL in this code, > it should hit

RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Charles Randall
. Charles -Original Message- From: Biju Susmer [mailto:b...@wipinfo.soft.net] Sent: Tuesday, August 17, 1999 3:25 AM Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE > > Well, yeah, that's becuase you're running i

RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Charles Randall
. Charles -Original Message- From: Biju Susmer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 17, 1999 3:25 AM Cc: [EMAIL PROTECTED] Subject: RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE > > Well, yeah, that's becuase you're running it out of swap by tryin

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Mark Newton
Biju Susmer wrote: > > Well, yeah, that's becuase you're running it out of swap by trying to > > allocate a gigabyte of memory. > > but this is done in steps of 1MB. Once it reaches out of memory, malloc > should return NULL. Since there is no checking for NULL in this code, > it should hi

RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Biju Susmer
> > Well, yeah, that's becuase you're running it out of swap by trying to > allocate a gigabyte of memory. but this is done in steps of 1MB. Once it reaches out of memory, malloc should return NULL. Since there is no checking for NULL in this code, it should hit a signal, isn't it? Why that is no

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Alec Kalinin
Hello ! > > I think, mentioned below program probably show the bug in virtual memory > > subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD >> comes into "out of swap" state, then hungs. >Well, yeah, that's becuase you're running it out of swap by trying to >allocate a gigaby

RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Biju Susmer
> > Well, yeah, that's becuase you're running it out of swap by trying to > allocate a gigabyte of memory. but this is done in steps of 1MB. Once it reaches out of memory, malloc should return NULL. Since there is no checking for NULL in this code, it should hit a signal, isn't it? Why that is n

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Mark Newton
Alec Kalinin wrote: > I think, mentioned below program probably show the bug in virtual memory > subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD comes > into "out of swap" state, then hungs. Well, yeah, that's becuase you're running it out of swap by trying to allocate a

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Alec Kalinin
Hello ! > > I think, mentioned below program probably show the bug in virtual memory > > subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD >> comes into "out of swap" state, then hungs. >Well, yeah, that's becuase you're running it out of swap by trying to >allocate a gigab

Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE

1999-08-17 Thread Mark Newton
Alec Kalinin wrote: > I think, mentioned below program probably show the bug in virtual memory > subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD comes > into "out of swap" state, then hungs. Well, yeah, that's becuase you're running it out of swap by trying to allocate