DiSL issueshttps://gitlab.ow2.org/disl/disl/-/issues2019-04-24T14:44:09Zhttps://gitlab.ow2.org/disl/disl/-/issues/11Explicit disl-bypass.jar load2019-04-24T14:44:09ZVít KabeleExplicit disl-bypass.jar loadWhen executing the analysis I sometimes forget to place the `disl-bypass.jar` into the observed program classpath, or the jar file is not present at its expected location
due to the build errors for example. In such cases the observed ma...When executing the analysis I sometimes forget to place the `disl-bypass.jar` into the observed program classpath, or the jar file is not present at its expected location
due to the build errors for example. In such cases the observed machine dies with a core dump by the NoClassDefFound exception that forces the user to read the JVM internal error messages to realise that he misused the api.
Since it's relatively frequented message I was wondering if it wouldn't be better to pass the path to the disl-bypass.jar as another parameter to the agent and then add
the path as the bootstrap classloader segment using the [AddToBootstrapClassloaderSearch](https://docs.oracle.com/javase/8/docs/platform/jvmti/jvmti.html#AddToBootstrapClassLoaderSearch) JVMTI method after we explicitly check whether the specified file exists.
It's not really must-have feature, but it would increase the user experience a bit.https://gitlab.ow2.org/disl/disl/-/issues/10Local socket transport2019-03-08T11:22:35ZVít KabeleLocal socket transportAdd support for locally created sockets (i.e. in domain *AF_UNIX*). This sockets are not addressed by a ip address, but its address is a file name.
Communication over the local socket makes a sense, when the analysis and the observed VM...Add support for locally created sockets (i.e. in domain *AF_UNIX*). This sockets are not addressed by a ip address, but its address is a file name.
Communication over the local socket makes a sense, when the analysis and the observed VM runs on the same physical machine, and allocating a port
is unnecessary.https://gitlab.ow2.org/disl/disl/-/issues/9Wiki/Web update2019-02-28T14:04:28ZVít KabeleWiki/Web updateI noticed, that there is a wiki page at [https://disl.ow2.org](https://disl.ow2.org).
As this page seems to be a bit discontinued I suppose to make a wiki as
[Gitlab Pages](https://docs.gitlab.com/ee/user/project/pages/),
if **OW** inst...I noticed, that there is a wiki page at [https://disl.ow2.org](https://disl.ow2.org).
As this page seems to be a bit discontinued I suppose to make a wiki as
[Gitlab Pages](https://docs.gitlab.com/ee/user/project/pages/),
if **OW** installation supports this feature. Since we have CI available, this shouldn't
bring much hassle and keeping the website managed from within a repository will bring us
a convenient way how to keep the documentation up-to-date with actual state of production
branch.
Even JavaDoc documentation can be simply included in generated website.https://gitlab.ow2.org/disl/disl/-/issues/8GIT workflow2018-11-27T14:06:35ZVít KabeleGIT workflowSince the disl is a project with relatively huge codebase, I think it would be nice to use some kind of well defined git workflow.
I’d suggest to use the **git flow** workflow, as described at [nvie.com](https://nvie.com/posts/a-success...Since the disl is a project with relatively huge codebase, I think it would be nice to use some kind of well defined git workflow.
I’d suggest to use the **git flow** workflow, as described at [nvie.com](https://nvie.com/posts/a-successful-git-branching-model/)