diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2011-07-25 11:27:24 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2011-07-25 11:27:24 +0200 |
| commit | b687f782572b127e8ae32f0df40250fb19ccd22b (patch) | |
| tree | ccce6af6cd4809f0f6fa694ff7789c52d1bb9c2e /open_issues/placement_of_virtual_memory_regions.mdwn | |
| parent | 6fb6c2a396bb1b851a4ec8a6f5e605a15c218d10 (diff) | |
| download | web-b687f782572b127e8ae32f0df40250fb19ccd22b.tar.gz web-b687f782572b127e8ae32f0df40250fb19ccd22b.tar.bz2 web-b687f782572b127e8ae32f0df40250fb19ccd22b.zip | |
IRC.
Diffstat (limited to 'open_issues/placement_of_virtual_memory_regions.mdwn')
| -rw-r--r-- | open_issues/placement_of_virtual_memory_regions.mdwn | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/open_issues/placement_of_virtual_memory_regions.mdwn b/open_issues/placement_of_virtual_memory_regions.mdwn index 95b9e545..39478f20 100644 --- a/open_issues/placement_of_virtual_memory_regions.mdwn +++ b/open_issues/placement_of_virtual_memory_regions.mdwn @@ -10,7 +10,7 @@ License|/fdl]]."]]"""]] [[!tag open_issue_gnumach]] -IRC, freenode, #hurd, 2011-07-13 +# IRC, freenode, #hurd, 2011-07-13 <braunr> does anyone know if posix (or mach) has requirements or a policy about the placement of allocations of virtual space ? @@ -87,3 +87,17 @@ IRC, freenode, #hurd, 2011-07-13 <braunr> jkoenig: i really want to miss as little as possible on the vm part, so having detailed information about what actually happens on running hurd systems is something i need + + +# IRC, freenode, #hurd, 2011-07-24 + + <braunr> oh btw, i noticed there are many mappings below the program text + <braunr> most notably, the stack + <braunr> except for special applications like wine, could this break + anything ? + <braunr> i also wonder how libraries are mapped, because there is nothing + to perform top-down allocations + <braunr> which means if the region below the program text is exhausted, + libraries could be mapped right after the heap + <youpi> it shouldn't break anything except things like wine & libgc, yes + <braunr> which could make malloc() fail :/ |