| Summary: | llpp gets segfault in r600g_dri.so | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | myxol <myxol> |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
gdb output and xorg.log
dmesg output mesa backtrace |
||
|
Description
myxol
2012-04-04 10:33:58 UTC
Can you get a proper backtrace with gdb? Can you also include your xorg log and dmesg output? Created attachment 59491 [details]
gdb output and xorg.log
gdb didn't produce any good backtrace. Could it be because llpp written in ocaml?
Created attachment 59492 [details]
dmesg output
Make sure you install the debugging symbols for the 3D driver/mesa. Most distros package these separately. Then when you hit the crash type "bt" in gdb to get the backtrace. Created attachment 59519 [details]
mesa backtrace
After playing with compilation flags to get meaningful backtrace I found that this segfault happens only with -O3… Dunno if this is considered as a bug.
Anyway, bt full attached. Mesa compiled with "-march=native -O3 -ggdb -pipe".
(In reply to comment #5) > After playing with compilation flags to get meaningful backtrace I found that > this segfault happens only with -O3… Dunno if this is considered as a bug. It's a bug *somewhere*, but it looks like it could be in the compiler... Maybe you can try isolating which specific option implied by -O3 but not by -O2 makes the difference. > Maybe you can try isolating which specific option implied by -O3 but not by -O2 makes the difference.
I tried. It is -ftree-vectorize
Smells more like a compiler bug then. Which version of gcc is this? Does it also happen with an older one? I tried 3 gcc versions. Flags: -march=native -O2 -ftree-vectorize -ggdb -pipe 4.4.7 - build fails 4.5.3 - original bugreport 4.6.2 - same problem as with 4.5.3 -- 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/407. |
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.