Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > comp.lang.java.machine > #3

Re: how JVM works

Show all headers | View raw

On Wed, 13 Apr 2011 17:31:41 -0400, Joshua Cranmer
<Pidgeot18@verizon.invalid> wrote, quoted or indirectly quoted someone
who said :

>
>The standard answer for shared libraries is that the read-only portions 
>of the library--i.e., .text, .rodata, etc. are loaded as read-only pages 
>in virtual memory, and each process that needs it has a pointer to this 
>page. Note that these pages are only created when they are loaded by the 
>DLL.

so every loaded DLL is visible to every process?? And appears at the
same virtual address to every process?

So DLLs are all public?  Any process can examine the code of any
loaded DLL?

-- 
Roedy Green Canadian Mind Products
http://mindprod.com
Doing what the user expects with respect to navigation is absurdly important for user satisfaction.
~ anonymous Google Android developer

Back to comp.lang.java.machine | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

how JVM works Roedy Green <see_website@mindprod.com.invalid> - 2011-04-13 12:36 -0700
  Re: how JVM works Joshua Cranmer <Pidgeot18@verizon.invalid> - 2011-04-13 17:31 -0400
    Re: how JVM works Roedy Green <see_website@mindprod.com.invalid> - 2011-04-13 14:36 -0700
      Re: how JVM works Joshua Cranmer <Pidgeot18@verizon.invalid> - 2011-04-13 19:26 -0400
    Re: how JVM works Roedy Green <see_website@mindprod.com.invalid> - 2011-04-13 14:42 -0700

csiph-web