[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259969] lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 21 Nov 2021 16:05:48 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259969 Bug ID: 259969 Summary: lib.libc.sys.setrlimit_test.setrlimit_stack fails with ASLR on by default Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: tests Assignee: testing@FreeBSD.org Reporter: emaste@freebsd.org Blocks: 259968 As reported by lwhsu and mw on -current, lib.libc.sys.setrlimit_test.setrlimit_stack fails after ASLR was enabled by default Process with PID 5957 exited with signal 11 and dumped core; attempting to gather stack trace [New LWP 101941] Core was generated by `setrlimit_test'. Program terminated with signal SIGSEGV, Segmentation fault. Invalid permissions for mapped object. #0 0x00002acc27fa3bc0 in ?? () #0 0x00002acc27fa3bc0 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffff8bde68 GDB exited successfully Files left in work directory after failure: setrlimit_test.core Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259968 [Bug 259968] ASLR by default tracking PR -- You are receiving this mail because: You are the assignee for the bug.