Re: [osv-dev] Re: Memory problem with Java multithreading application in OSv

2019-05-20 Thread robertob
Il giorno lunedì 20 maggio 2019 18:09:49 UTC+2, Nadav Har'El ha scritto: > > > On Mon, May 20, 2019 at 5:35 PM Waldek Kozaczuk > wrote: > >> >> >> On Sunday, May 19, 2019 at 12:19:59 PM UTC-4, robertob wrote: >>> >>> Hi everybody, >>> >>> I have built an OSv image that run with QEMU and KVM

Re: [osv-dev] Modernizing and cleaning build system

2019-05-20 Thread Nadav Har'El
On Mon, May 20, 2019 at 6:48 PM Waldek Kozaczuk wrote: > In the next couple of weeks I will be trying to work on some of those > issues. I think that eliminating external and fixing "openssl 1.0" issue > are probably most pressing ones. I feel like we have gotten to the point > where are some of

Re: [osv-dev] Re: Memory problem with Java multithreading application in OSv

2019-05-20 Thread Nadav Har'El
On Mon, May 20, 2019 at 5:35 PM Waldek Kozaczuk wrote: > > > On Sunday, May 19, 2019 at 12:19:59 PM UTC-4, robertob wrote: >> >> Hi everybody, >> >> I have built an OSv image that run with QEMU and KVM acceleration. It >> executes a mine Java multi threading application. >> >> This is the

Re: [osv-dev] Modernizing and cleaning build system

2019-05-20 Thread Waldek Kozaczuk
In the next couple of weeks I will be trying to work on some of those issues. I think that eliminating external and fixing "openssl 1.0" issue are probably most pressing ones. I feel like we have gotten to the point where are some of these issues start hindering the development of the project.

[osv-dev] Re: Memory problem with Java multithreading application in OSv

2019-05-20 Thread robertob
I create the Threads in the same Java with this instruction: new Thread(...) { } I think these are Java threads...or not? yes I used VisualVM and it allocates no more then the heap allocated with the Xmx arguments to the Java executable. Infact Java does not fail for memory, it fails the

[osv-dev] Re: Memory problem with Java multithreading application in OSv

2019-05-20 Thread Waldek Kozaczuk
On Sunday, May 19, 2019 at 12:19:59 PM UTC-4, robertob wrote: > > Hi everybody, > > I have built an OSv image that run with QEMU and KVM acceleration. It > executes a mine Java multi threading application. > > This is the command line I execute: > > capstan run unikure -n "bridge" -c 2 -m

[osv-dev] [COMMIT osv master] Added option suffix "!" to force termination of remaining application threads

2019-05-20 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Nadav Har'El Branch: master Added option suffix "!" to force termination of remaining application threads Some applications like JVM leave other threads running after main thread terminates. OSv is pedantic about it and likes to keep application running

[osv-dev] [COMMIT osv master] Move _post_main invocation to run_main

2019-05-20 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Nadav Har'El Branch: master Move _post_main invocation to run_main This patch also fixes __libc_start_main() used for example by java to terminate any remaining app threads by _post_main. Signed-off-by: Waldemar Kozaczuk Message-Id:

[osv-dev] [COMMIT osv master] vfs: Harden task_conv() to return EFAULT when cpath argument is null

2019-05-20 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Nadav Har'El Branch: master vfs: Harden task_conv() to return EFAULT when cpath argument is null This patch also reverts the commit a0dcf8530c352536ab6633952b6f614f73eed154. Signed-off-by: Waldemar Kozaczuk Message-Id:

[osv-dev] [COMMIT osv master] Enhanced __fxstata to handle AT_SYMLINK_NOFOLLOW

2019-05-20 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Nadav Har'El Branch: master Enhanced __fxstata to handle AT_SYMLINK_NOFOLLOW This patch also effectively makes unmodified coreutils find work as expected: ./scripts/manifest_from_host.sh -w find && ./scripts/build fs=rofs --append-manifest