On Wed, May 3, 2017 at 11:31 AM, Thomas Stüfe
wrote:
> Hi Alan,
>
> thanks! One more question: I find no platform dependent coding on for the
> shared memory transport layer for Unix, just for Windows. I would have
> expected some mmap() calls somewhere, and a LoadLibrary(dt_shmem). Looking
> clo
Hi Alan,
thanks! One more question: I find no platform dependent coding on for the
shared memory transport layer for Unix, just for Windows. I would have
expected some mmap() calls somewhere, and a LoadLibrary(dt_shmem). Looking
closer, I also cannot find a libdt_shmem.so on a jdk10 linux build.
On 03/05/2017 09:47, Thomas Stüfe wrote:
:
And for the socket transport, it is not needed at the jdi side because
there the socket transport is reimplemented in pure java?
That's right. If there was an issue with the socket transport then it
would have been fixed a long time ago - the reas
Hi Alan,
On Wed, May 3, 2017 at 9:03 AM, Alan Bateman
wrote:
> On 03/05/2017 07:43, Thomas Stüfe wrote:
>
> Hi all,
>>
>> I wonder why the sources of the transport libraries are located in
>> different places:
>>
>> jdk/src/jdk.jdwp.agent/share/native/libdt_socket
>> jdk/src/jdk.jdi/share/nativ
On 03/05/2017 07:43, Thomas Stüfe wrote:
Hi all,
I wonder why the sources of the transport libraries are located in
different places:
jdk/src/jdk.jdwp.agent/share/native/libdt_socket
jdk/src/jdk.jdi/share/native/libdt_shmem
Is there a particular reason to this?
Seeing as they both are impl
