On Sun, 2008-06-08 at 20:38 +0400, Andrew Vagin wrote:
> 2008/6/8 Subrata Modak <[EMAIL PROTECTED]>:
> > The Patch makes the test case to be executed as root. I executed pre and
> > post patch. Post patch allows me to execute only as root. Do you think
> > we need to introduce this burden. Modify it to avoid this dependency.
> >
> > $ ./testcases/bin/mallocstress
> > semop: Permission denied
> sorry, forgot set permission in semget, new patch attached.

Thanks. Applied.

Regards--
Subrata

> >
> > Regards--
> > Subrata
> >
> > On Sat, 2008-06-07 at 14:02 +0400, Andrew Vagin wrote:
> >> mallocstress  return fail sometimes.
> >> [EMAIL PROTECTED] mtest07]# ./mallocstress -t 30
> >> main(): pthread_create(): Cannot allocate memory
> >> [EMAIL PROTECTED] mtest07]# echo $?
> >> 255
> >>
> >> mallocstress stresses the VMM and C library  by spawning N threads
> >> which
> >> malloc blocks of increasing size until malloc returns NULL.
> >>
> >> It occur because test doesn't wait for all thread started.
> >> already started threads begin allocate memory, so pthread_create can
> >> return ENOMEM.
> >> my patch added this synchronizing.
> >> I use semaphore, because it can wait-for-zero unlike pthread_mutex
> >> -------------------------------------------------------------------------
> >> Check out the new SourceForge.net Marketplace.
> >> It's the best place to buy or sell services for
> >> just about anything Open Source.
> >> http://sourceforge.net/services/buy/index.php
> >> _______________________________________________ Ltp-list mailing list 
> >> [email protected] 
> >> https://lists.sourceforge.net/lists/listinfo/ltp-list
> >
> >


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to