http://bugzilla.suse.com/show_bug.cgi?id=962609
http://bugzilla.suse.com/show_bug.cgi?id=962609#c2
Egbert Eich
Current leap with updates.
First the beef: vlc crashes, gdb thankfully reports all required -debuginfo packages, zypper installs them. But finally libvdpau_r600-debuginfo-11.0.8-134.1.x86_64 is missing.
Looks like libvdpau_r600.rpm is built without -g, or the debuginfo is not packaged for some reason?
Name : libvdpau_r600 Source RPM : Mesa-11.0.8-134.1.src.rpm
Now the noise: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffad087700 (LWP 12869)] dri_flush (cPriv=0x100000000, dPriv=0x7fffa817bea0, flags=1, ^^^^^ This is a pointer. However the value is strange. It sort of looks like it is some sort of canary. Ultimately it's the same pointer (ie context) as
No. This is probably because libvdpau_<i> for <i>={noveau, r300, r600, radeonsi} are all a hard link to libvdpau_gallium. Things should be packaged differently probably: We can only preserve the hard links if we put all libs into a single package. With this we may even get hard-linked debuginfos. @Stefan: Could you look into this? Looking into this I however found something rather strange in the buildservice log: [ 1025s] + /usr/lib/rpm/find-debuginfo.sh /home/abuild/rpmbuild/BUILD/mesa-11.1.0 [ 1025s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/Mesa-11.1.0-130.1.x86_64/usr/lib64/d3d/d3dadapter9.so.1.0.0 [ 1026s] file /home/abuild/rpmbuild/BUILDROOT/Mesa-11.1.0-130.1.x86_64/usr/lib64/dri/i915_dri.so has 4 other hard links [ 1026s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/Mesa-11.1.0-130.1.x86_64/usr/lib64/dri/i915_dri.so [ 1027s] file /home/abuild/rpmbuild/BUILDROOT/Mesa-11.1.0-130.1.x86_64/usr/lib64/dri/kms_swrast_dri.so has 6 other hard links [ 1027s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/Mesa-11.1.0-130.1.x86_64/usr/lib64/dri/kms_swrast_dri.so [..] [ 1036s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/Mesa-11.1.0-130.1.x86_64/usr/lib64/vdpau/libvdpau_nouveau.so.1.0.0 [ 1039s] cpio: glibc-2.22/csu: Cannot stat: No such file or directory [ 1039s] cpio: glibc-2.22/include/stdlib.h: Cannot stat: No such file or directory [ 1039s] cpio: glibc-2.22/stdlib: Cannot stat: No such file or directory [ 1039s] cpio: glibc-2.22/stdlib/atexit.c: Cannot stat: No such file or directory [ 1039s] cpio: glibc-2.22/sysdeps/x86_64/crti.S: Cannot stat: No such file or directory [ 1039s] cpio: glibc-2.22/sysdeps/x86_64/crtn.S: Cannot stat: No such file or directory [ 1040s] cpio: src/glsl/glcpp/glcpp-lex.l: Cannot stat: No such file or directory [ 1040s] cpio: src/glsl/glcpp/glcpp-parse.y: Cannot stat: No such file or directory [ 1040s] cpio: src/glsl/glsl_lexer.ll: Cannot stat: No such file or directory [ 1040s] cpio: src/glsl/glsl_parser.yy: Cannot stat: No such file or directory [ 1040s] cpio: src/mesa/program/program_lexer.l: Cannot stat: No such file or directory [ 1040s] cpio: src/mesa/program/program_parse.y: Cannot stat: No such file or directory [ 1040s] 89854 blocks Not sure why this happens. @Michael, do you hae an idea what's happening here? the GLX context. At first glance you may want to put a watchpoint on __glX_tls_Context and see who wedges it.
reason=__DRI2_THROTTLE_SWAPBUFFER) at dri_drawable.c:444 444 struct dri_context *ctx = dri_context(cPriv); Missing separate debuginfos, use: zypper install libvdpau_r600-debuginfo-11.0.8-134.1.x86_64 (gdb) up #1 0x00007fffe86a8bae in dri2SwapBuffers (pdraw=0x7fffa817ac70, target_msc=0, divisor=0, remainder=0, flush=0) at dri2_glx.c:851 851 dri2Flush(psc, ctx, priv, flags, __DRI2_THROTTLE_SWAPBUFFER); (gdb) l 846 } else { 847 __DRIcontext *ctx = dri2GetCurrentContext(); ^^^^^ This one.
848 unsigned flags = __DRI2_FLUSH_DRAWABLE; 849 if (flush) 850 flags |= __DRI2_FLUSH_CONTEXT; 851 dri2Flush(psc, ctx, priv, flags, __DRI2_THROTTLE_SWAPBUFFER); ^^^ |||
852 853 ret = dri2XcbSwapBuffers(pdraw->psc->dpy, pdraw, 854 target_msc, divisor, remainder); 855 } (gdb) p priv $1 = (struct dri2_drawable *) 0x7fffa817ac70
Nope, not this one.(In reply to Olaf Hering from comment #1)
The required debuginfo is available in TW.
(In reply to Olaf Hering from comment #1)
The required debuginfo is available in TW.
Where do you see this? -- You are receiving this mail because: You are on the CC list for the bug.