Hi,

Please take a look at:
spoj.sphere.pl/forum/viewtopic.p ... mory+usage250
spoj.sphere.pl/forum/viewtopic.p ... mory+usage145
The essence of BSD process accounting is in fact similar to regular polling of /proc. The use of RLIMITs serves as an additional, deterministically reliable restriction.

Well.. it's the C library; if you want to save some memory, write in asm or at least don't use glibc
As you noticed, shared libraries are also counted, as well as the binary itself. In spoj, a C program which does nothing is reported to consume quite a lot of memory (glibc), while fpc programs don't (dyniamic linking doesn't work (?)).

Um.. I don't know what you mean.. AFAIK every process is guaranteed to be logged after it finishes (and its parent wait()s for it). And I don't know what "**other" is, maybe I haven't looked into "sa" enough.. I use "dump-acct" myself and in spoj we process pacct files on our own.

In spoj, we just output the average memory usage of the first process. If you want to measure maximum memory usage, polling /proc is the only thing I can think of.
I think average isn't that bad; and processes are guaranteed not to exceed fixed memory limit set by RLIMITs.

All dynamic libraries it's linked with, program's code itself and all data and stack memory it allocates, AFAIK.
They are kilobytes, glibc is quite heavy. But then again, it's sure to be cached in RAM.

Well, if your distribution doesn't come with it, google for it..
Fields are: command, user time, system time, effective time, uid, gid, memory, io, time.

It's allocated memory, not accessed. I don't know how to measure accessed memory.

We don't Right now, it's "RE (other)" in spoj.
We might start to detect it sometime, but I personally don't like to mess with ptrace() and we would detach after loading libraries and allocating memory anyway.

I don't get your point, on my systems, chroot() doesn't give any additional privileges and unlink()ing is at least as hard without proper privileges as without it.
And yes, we have separate chroot or two (chroots for compilers) for all languages.
Input and output files are passed though pipes.

Of course it does! Memory limits never had been "strict" in spoj: RLIMIS_AS is set to 256MB (enough to keep JVM happy), 64MB of physical RAM is guaranteed for the program itself and that's it.
It might seem desperate, but I can't think of a "problem" where a set memory limit would really be necessary.
Such problem would have to be limited to few languages (C/C++/Pascal?), programs would have to be linked statically and even then, compiler's optimizer could break a program which seems to use little memory enough.
Note that online judges which compile statically and have ~3 languages to choose from don't have such problems :>

Memory usage of those SIGSEGVs isn't greater than the limit - it's really low instead. IMO, ptrace() would be more trustworty than comparing that value to observed memory consumption of SIGSEGVed program for a specific language.
With ptrace(), it would be enough to check what execve() returns.

strace-ing execve() of a program which allocates more memory at the very start (from ELF headers, not in the code) gives:
execve("./a", ["./a"], [/* 23 vars */]) = -1 ENOMEM (Cannot allocate memory)
+++ killed by SIGKILL +++
That's the only time where allocating memory results is SIGSEGV, e.g. malloc-ing simply fails when reaching the limit. And it's nothing wrong to allocate as much memory as you can this way (large malloc, halve the amount you want if it fails etc).

We are left with using operating system specific APIs to determine memory usage. This is however, an advantage. We will be able to determine the complete overhead of an application, including memory not allocated through the C library. For example, when the process loads a shared library, the linker will use the mmap() system call directly. Similarly, the thread stacks in the pthread implementation will be directly mapped rather than malloced.

Tak to już jest, z przechodzeniem, że potem robią się z tego problemy po przejściach.
Podstawowy problem polega tu na tym, że powinien przebiegać, a nie przechodzić. Jak dalej będzie się tak guzdrał, to dla niepodstawowych będzie dużo za wolny, tak przynajmniej czuję i mogę się domyślić i wyobraźić.

Jak Ci mogę jeszcze pomóc?

Ewentualnie, jak Ty byś trochę mógł pomóc, tym co Ci chcieliby ewentualnie pomóc, w ten sposób, żebyś pomógł im, aby mogli lepiej zrozumieć jak Ci pomóc, żebyś mógł lepiej pomóc tym, którzy zechcą Ci pomóc... chyba się zapętliłem w rekurencję.

Jak to zrobić? Gdzieś tam na forum leży taki jakiś poradnik.

Ok. rozumiem. Z tym, że chwilowo nie chodzi mi o to aby ten program przebiegał przez testy tylko żeby je zrobił. Nie wyrzuca mi, że przekroczyłem limit czasu tylko, że jest błędna odpowiedź. Tak po za tym w limicie czasu na razie się mieści, ma jeszcze zapas sekundy.

Chodzi mi o to, że nie mogę znaleźć testu dla którego pojawia się błędna odpowiedź. Kod jest napisany chyba dość przejrzyście.

Z tego co widziałem na forum, wszyscy wrzucają tak kody, do tego kod chyba nie jest za długi.

Zadanie zaakceptowane, co prawda na razie dosyć słabą metodyką (choć i tak skrócone o te warunki) ale zaraz sobie przerobię żeby działało rekurencyjnie. Dzięki wielkie za sugestie, w tym również to, że funkcja potęgi jest zbędna oraz za te nie dotyczące zadania. Na pewno to usprawni moją komunikacje na forum.

Yes, links are broken. Could you restore that information please?