https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
Dmitry Chagin changed:
What|Removed |Added
Assignee|emulat...@freebsd.org |dcha...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #15 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=b1d0fe755bb11be36d97885dbab0ac66aabb5877
commit b1d0fe755bb11be36d97885dbab0ac66aabb5877
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
Ed Maste changed:
What|Removed |Added
Status|New |In Progress
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #14 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=ef1976ccf5420d0912afcb49733c7a88643069da
commit ef1976ccf5420d0912afcb49733c7a88643069da
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
Edward Tomasz Napierala changed:
What|Removed |Added
Blocks||247219
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #13 from Alex S ---
(In reply to Alex S from comment #12)
OK, just for completeness, FreeBSD — pretty accurate, Linux — only for initial
thread: https://gist.github.com/shkhln/af421368a36727926ad9103e8f59b455.
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #12 from Alex S ---
(In reply to Conrad Meyer from comment #11)
Rampant copy-pasting finally got me, ROFL.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #11 from Conrad Meyer ---
You need to use /proc/getpid()/maps — your most recent demo is showing cat’s
memory map.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #10 from Alex S ---
(In reply to Conrad Meyer from comment #8)
I noticed neither Linux nor FreeBSD actually bothers with accurate
stack mappings in /proc/self/map. About multiple threads Linux's
documentation plainly states "[s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #9 from Conrad Meyer ---
I think this may have been introduced in r320317 (19bd0d9c85cc):
Implement address space guards.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #8 from Conrad Meyer ---
Sure, we could also just try to hide that entry. I'm honestly not sure what
the point of the explicit --- mapping is for.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #7 from Conrad Meyer ---
In exec, we map the stack with vm_map_stack() with rlim_cur (I think); in
vm_map_stack, we set the init_ssize with MIN(sysctl kern.sgrowsiz, rlim_cur).
kern.sgrowsiz is 128kB.
There's a comment about
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #6 from Alex S ---
(In reply to Conrad Meyer from comment #5)
Yep, that's pretty much it. Do you think it makes sense to just hide that
entry?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #5 from Conrad Meyer ---
Ok, here's what's going on:
Our rlimit value (cur) is fine; same as glibc (8MB).
Glibc is parsing /proc/self/maps to limit the pthread "stack size" based on
adjacent mappings, *which it assumes cannot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
15 matches
Mail list logo
