| Summary: | Xwayland segv on startup | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | henrik.riomar |
| Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 18.2 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
gbg backtrace with mesa debug symbols
gbg backtrace without mesa debug symbols |
||
Created attachment 142793 [details]
gbg backtrace without mesa debug symbols
Running Alpine Linux (musl libc) Would you be able to wrap Xwayland into valgrind and attach the traces? That would help to figure out what memory was freed. Using the patch from here: https://git.alpinelinux.org/cgit/aports/commit/?id=ff8996cea00e39d93c869434e263268eab704591 with 18.2.6 solves the issue for me -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1775. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 142792 [details] gbg backtrace with mesa debug symbols Xwayland(1.20.3) SIGSEGV on startup with mesa 18.2.6 gdb back traces from the core file attached.