Github messages for voidlinux
 help / Atom feed
* [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
@ 2019-06-30 18:16 voidlinux-github
  2019-07-01  8:20 ` voidlinux-github
                   ` (12 more replies)
  0 siblings, 13 replies; 14+ messages in thread
From: voidlinux-github @ 2019-06-30 18:16 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 4693 bytes --]

New issue by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760
Description: ### System

* xuname:  
  Void 5.1.15_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFFFF
* package:  
  mesa-nouveau-dri-dbg-19.1.1_1

### Expected behavior

`gdb` should load debug symbols for the right file, i.e. `/usr/lib/debug/vdpau/libvdpau_nouveau.so.1` should match `/usr/lib/vdpau/libvdpau_nouveau.so.1`, etc., backtrace should contain symbols for all loaded libraries, etc.

### Actual behavior

`gdb` gives debug information mismatch warning, backtrace is missing details

### Steps to reproduce the behavior

(trying to debug void-linux/void-packages#12717)

* On a system using `nouveau` X graphics driver and `gdb` installed, run the following in a terminal:
```sh
# xbps-install vdpauinfo{,-dbg} glibc-dbg mesa-nouveau-dri-dbg
```
* Run `vdpauinfo` under GDB

Results on my system:
```sh
$ gdb -q vdpauinfo 
Reading symbols from vdpauinfo...
Reading symbols from /usr/lib/debug//usr/bin/vdpauinfo...
(gdb) set pagination off 
(gdb) run
Starting program: /usr/bin/vdpauinfo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
display: :0   screen: 0
warning: the debug information found in "/usr/lib/vdpau/libvdpau_r300.so.1.0.0" does not match "/usr/lib/vdpau/libvdpau_nouveau.so.1" (CRC mismatch).

warning: the debug information found in "/usr/lib/vdpau/libvdpau_r300.so.1.0.0" does not match "/usr/lib/vdpau/libvdpau_nouveau.so.1" (CRC mismatch).

[New Thread 0x7fffefbda700 (LWP 11586)]

Thread 1 "vdpauinfo" received signal SIGSEGV, Segmentation fault.
0x00007ffff72b2937 in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
(gdb) bt full
#0  0x00007ffff72b2937 in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#1  0x00007ffff72c1696 in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#2  0x00007ffff7288210 in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#3  0x00007ffff72882bf in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#4  0x00007ffff72b0deb in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#5  0x00007ffff72859b7 in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#6  0x00007ffff72ddceb in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#7  0x00007ffff72e5dac in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#8  0x00007ffff70034f3 in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#9  0x00007ffff6ffcf2a in ?? () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#10 0x00007ffff6fecdcb in vdp_imp_device_create_x11 () from /usr/lib/vdpau/libvdpau_nouveau.so.1
No symbol table info available.
#11 0x00007ffff7e6daf5 in vdp_device_create_x11 () from /usr/lib/libvdpau.so.1
No symbol table info available.
#12 0x00005555555554ad in main (argc=<optimized out>, argv=0x7fffffffe198) at vdpauinfo.cpp:488
        o = {
          display_name = 0x7fffffffeb53 ":0", 
          screen = <optimized out>
        }
        display = 0x55555576ce70
        screen = 0
        device = 1
        get_proc_address = 0x1
        rv = <optimized out>
        impl = <optimized out>
(gdb) 
```

Running `objdump -g` on the debug information file confirms the incorrect link:
```sh
$ objdump -g /usr/lib/debug/usr/lib/vdpau/libvdpau_nouveau.so.1.0.0

/usr/lib/debug/usr/lib/vdpau/libvdpau_nouveau.so.1.0.0:     file format elf64-x86-64

objdump: Warning: could not find separate debug file 'libvdpau_r300.so.1.0.0'
objdump: Warning: tried: /lib/debug/libvdpau_r300.so.1.0.0
objdump: Warning: tried: /usr/lib/debug/usr/libvdpau_r300.so.1.0.0
objdump: Warning: tried: /usr/lib/debug/libvdpau_r300.so.1.0.0
objdump: Warning: tried: /usr/lib/debug/usr/lib/vdpau/.debug/libvdpau_r300.so.1.0.0
objdump: Warning: tried: /usr/lib/debug/usr/lib/vdpau/libvdpau_r300.so.1.0.0
objdump: Warning: tried: .debug/libvdpau_r300.so.1.0.0
objdump: Warning: tried: libvdpau_r300.so.1.0.0

Section '.eh_frame' has an invalid size: 0x8bfb0.
Contents of the .gnu_debuglink section (loaded from /usr/lib/debug/usr/lib/vdpau/libvdpau_nouveau.so.1.0.0):

  Separate debug info file: libvdpau_r300.so.1.0.0
  CRC value: 0x69940ea

```

My guess is that something went wrong during build or packaging. I haven't looked into it, so I don't know if the problem is with the recipe or with `xbps-src` itself.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
@ 2019-07-01  8:20 ` voidlinux-github
  2019-07-01  8:24 ` voidlinux-github
                   ` (11 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01  8:20 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file.
For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so.1.0.0`, all eventually pointing to `libvdpau_gallium.so.1.0.0`.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
  2019-07-01  8:20 ` voidlinux-github
@ 2019-07-01  8:24 ` voidlinux-github
  2019-07-01  8:30 ` voidlinux-github
                   ` (10 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01  8:24 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file by `${wrksrc}/bin/install_megadrivers.py`.

For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so.1.0.0`, all eventually pointing to `libvdpau_gallium.so.1.0.0`.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
  2019-07-01  8:20 ` voidlinux-github
  2019-07-01  8:24 ` voidlinux-github
@ 2019-07-01  8:30 ` voidlinux-github
  2019-07-01  8:35 ` voidlinux-github
                   ` (9 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01  8:30 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file by `${wrksrc}/bin/install_megadrivers.py`.

For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so.1.0.0`, all eventually pointing to `libvdpau_gallium.so`. It appears that `xbps-src`'s `common/hooks/post-install/06-strip-and-debug-pkgs.sh` doesn't know how to deal with those multi-symlinks.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (2 preceding siblings ...)
  2019-07-01  8:30 ` voidlinux-github
@ 2019-07-01  8:35 ` voidlinux-github
  2019-07-01 16:14 ` voidlinux-github
                   ` (8 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01  8:35 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file by `${wrksrc}/bin/install_megadrivers.py`.

For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so.1.0.0`, all eventually pointing to `libvdpau_gallium.so`. It appears that `xbps-src`'s `common/hooks/post-install/06-strip-and-debug-pkgs.sh` doesn't handle these correctly.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (3 preceding siblings ...)
  2019-07-01  8:35 ` voidlinux-github
@ 2019-07-01 16:14 ` voidlinux-github
  2019-07-01 16:30 ` voidlinux-github
                   ` (7 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01 16:14 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3345 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507331014
Comment:
Anyway, after installing the `mesa-ati-dri-dbg` package, I get the following backtrace with a bit more detail:
```sh
$ gdb -q vdpauinfo
Reading symbols from vdpauinfo...
Reading symbols from /usr/lib/debug//usr/bin/vdpauinfo...
(gdb) set pagination off 
(gdb) run
Starting program: /usr/bin/vdpauinfo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
display: :0   screen: 0
warning: the debug information found in "/usr/lib/vdpau/libvdpau_r300.so.1.0.0" does not match "/usr/lib/vdpau/libvdpau_nouveau.so.1" (CRC mismatch).

[New Thread 0x7fffefbda700 (LWP 22843)]

Thread 1 "vdpauinfo" received signal SIGSEGV, Segmentation fault.
nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
2085	../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp: No such file or directory.
(gdb) bt
#0  nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
#1  0x00007ffff72c1696 in nv50_ir::AlgebraicOpt::visit (this=0x7fffffffc140, bb=<optimized out>) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2351
#2  0x00007ffff7288210 in nv50_ir::Pass::doRun (this=0x7fffffffc140, func=<optimized out>, ordered=<optimized out>, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_bb.cpp:500
#3  0x00007ffff72882bf in nv50_ir::Pass::doRun (this=0x7fffffffc140, prog=<optimized out>, ordered=false, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_inlines.h:413
#4  0x00007ffff72b0deb in nv50_ir::Program::optimizeSSA (this=this@entry=0x5555557ecdb0, level=3) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:4005
#5  0x00007ffff72859b7 in nv50_ir_generate_code (info=info@entry=0x5555558440b0) at ../src/gallium/drivers/nouveau/codegen/nv50_ir.cpp:1267
#6  0x00007ffff72ddceb in nvc0_program_translate (prog=prog@entry=0x55555582b5a0, chipset=<optimized out>, debug=debug@entry=0x5555557e7798) at ../src/gallium/drivers/nouveau/nvc0/nvc0_program.c:638
#7  0x00007ffff72e5dac in nvc0_cp_state_create (pipe=0x5555557e73d0, cso=0x7fffffffce20) at ../src/gallium/drivers/nouveau/nvc0/nvc0_context.h:292
#8  0x00007ffff70034f3 in vl_compositor_cs_create_shader (c=c@entry=0x5555557c18b8, compute_shader_text=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor_cs.c:433
#9  0x00007ffff6ffcf2a in init_shaders (c=0x5555557c18b8) at ../src/gallium/auxiliary/vl/vl_compositor.c:74
#10 vl_compositor_init (c=c@entry=0x5555557c18b8, pipe=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor.c:767
#11 0x00007ffff6fecdcb in vdp_imp_device_create_x11 (display=<optimized out>, screen=<optimized out>, device=0x7fffffffe03c, get_proc_address=0x7fffffffdfd8) at ../src/gallium/state_trackers/vdpau/device.c:129
#12 0x00007ffff7e6daf5 in vdp_device_create_x11 () from /usr/lib/libvdpau.so.1
#13 0x00005555555554ad in main (argc=<optimized out>, argv=0x7fffffffe168) at vdpauinfo.cpp:488
```
Although there's still a warning, at least the symbol names look somewhat reasonable.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (4 preceding siblings ...)
  2019-07-01 16:14 ` voidlinux-github
@ 2019-07-01 16:30 ` voidlinux-github
  2019-07-01 16:34 ` voidlinux-github
                   ` (6 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01 16:30 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3416 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507331014
Comment:
Anyway, after installing the `mesa-ati-dri-dbg` package, I get the following backtrace with a bit more detail:
```sh
$ gdb -q vdpauinfo
Reading symbols from vdpauinfo...
Reading symbols from /usr/lib/debug//usr/bin/vdpauinfo...
(gdb) directory /masterdir/builddir/mesa-19.1.1/build
Source directories searched: /masterdir/builddir/mesa-19.1.1/build:$cdir:$cwd
(gdb) set pagination off 
(gdb) run
Starting program: /usr/bin/vdpauinfo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
display: :0   screen: 0
warning: the debug information found in "/usr/lib/vdpau/libvdpau_r300.so.1.0.0" does not match "/usr/lib/vdpau/libvdpau_nouveau.so.1" (CRC mismatch).

[New Thread 0x7fffefbda700 (LWP 23390)]

Thread 1 "vdpauinfo" received signal SIGSEGV, Segmentation fault.
nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590)
    at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
2085	   if (insn->saturate ||
(gdb) bt
#0  nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
#1  0x00007ffff72c1696 in nv50_ir::AlgebraicOpt::visit (this=0x7fffffffc140, bb=<optimized out>) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2351
#2  0x00007ffff7288210 in nv50_ir::Pass::doRun (this=0x7fffffffc140, func=<optimized out>, ordered=<optimized out>, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_bb.cpp:500
#3  0x00007ffff72882bf in nv50_ir::Pass::doRun (this=0x7fffffffc140, prog=<optimized out>, ordered=false, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_inlines.h:413
#4  0x00007ffff72b0deb in nv50_ir::Program::optimizeSSA (this=this@entry=0x5555557ecdb0, level=3) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:4005
#5  0x00007ffff72859b7 in nv50_ir_generate_code (info=info@entry=0x5555558440b0) at ../src/gallium/drivers/nouveau/codegen/nv50_ir.cpp:1267
#6  0x00007ffff72ddceb in nvc0_program_translate (prog=prog@entry=0x55555582b5a0, chipset=<optimized out>, debug=debug@entry=0x5555557e7798) at ../src/gallium/drivers/nouveau/nvc0/nvc0_program.c:638
#7  0x00007ffff72e5dac in nvc0_cp_state_create (pipe=0x5555557e73d0, cso=0x7fffffffce20) at ../src/gallium/drivers/nouveau/nvc0/nvc0_context.h:292
#8  0x00007ffff70034f3 in vl_compositor_cs_create_shader (c=c@entry=0x5555557c18b8, compute_shader_text=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor_cs.c:433
#9  0x00007ffff6ffcf2a in init_shaders (c=0x5555557c18b8) at ../src/gallium/auxiliary/vl/vl_compositor.c:74
#10 vl_compositor_init (c=c@entry=0x5555557c18b8, pipe=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor.c:767
#11 0x00007ffff6fecdcb in vdp_imp_device_create_x11 (display=<optimized out>, screen=<optimized out>, device=0x7fffffffe03c, get_proc_address=0x7fffffffdfd8) at ../src/gallium/state_trackers/vdpau/device.c:129
#12 0x00007ffff7e6daf5 in vdp_device_create_x11 () from /usr/lib/libvdpau.so.1
#13 0x00005555555554ad in main (argc=<optimized out>, argv=0x7fffffffe168) at vdpauinfo.cpp:488
```
Although there's still a warning, at least the symbol names now look reasonable.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (5 preceding siblings ...)
  2019-07-01 16:30 ` voidlinux-github
@ 2019-07-01 16:34 ` voidlinux-github
  2019-07-01 16:49 ` voidlinux-github
                   ` (5 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01 16:34 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3521 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507331014
Comment:
Anyway, after installing the `mesa-ati-dri-dbg` package, I get the following backtrace with a bit more detail:
```sh
$ gdb -q vdpauinfo
Reading symbols from vdpauinfo...
Reading symbols from /usr/lib/debug//usr/bin/vdpauinfo...
(gdb) directory /masterdir/builddir/mesa-19.1.1/build
Source directories searched: /masterdir/builddir/mesa-19.1.1/build:$cdir:$cwd
(gdb) set pagination off 
(gdb) run
Starting program: /usr/bin/vdpauinfo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
display: :0   screen: 0
warning: the debug information found in "/usr/lib/vdpau/libvdpau_r300.so.1.0.0" does not match "/usr/lib/vdpau/libvdpau_nouveau.so.1" (CRC mismatch).

[New Thread 0x7fffefbda700 (LWP 23390)]

Thread 1 "vdpauinfo" received signal SIGSEGV, Segmentation fault.
nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590)
    at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
2085	   if (insn->saturate ||
(gdb) bt
#0  nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
#1  0x00007ffff72c1696 in nv50_ir::AlgebraicOpt::visit (this=0x7fffffffc140, bb=<optimized out>) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2351
#2  0x00007ffff7288210 in nv50_ir::Pass::doRun (this=0x7fffffffc140, func=<optimized out>, ordered=<optimized out>, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_bb.cpp:500
#3  0x00007ffff72882bf in nv50_ir::Pass::doRun (this=0x7fffffffc140, prog=<optimized out>, ordered=false, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_inlines.h:413
#4  0x00007ffff72b0deb in nv50_ir::Program::optimizeSSA (this=this@entry=0x5555557ecdb0, level=3) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:4005
#5  0x00007ffff72859b7 in nv50_ir_generate_code (info=info@entry=0x5555558440b0) at ../src/gallium/drivers/nouveau/codegen/nv50_ir.cpp:1267
#6  0x00007ffff72ddceb in nvc0_program_translate (prog=prog@entry=0x55555582b5a0, chipset=<optimized out>, debug=debug@entry=0x5555557e7798) at ../src/gallium/drivers/nouveau/nvc0/nvc0_program.c:638
#7  0x00007ffff72e5dac in nvc0_cp_state_create (pipe=0x5555557e73d0, cso=0x7fffffffce20) at ../src/gallium/drivers/nouveau/nvc0/nvc0_context.h:292
#8  0x00007ffff70034f3 in vl_compositor_cs_create_shader (c=c@entry=0x5555557c18b8, compute_shader_text=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor_cs.c:433
#9  0x00007ffff6ffcf2a in init_shaders (c=0x5555557c18b8) at ../src/gallium/auxiliary/vl/vl_compositor.c:74
#10 vl_compositor_init (c=c@entry=0x5555557c18b8, pipe=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor.c:767
#11 0x00007ffff6fecdcb in vdp_imp_device_create_x11 (display=<optimized out>, screen=<optimized out>, device=0x7fffffffe03c, get_proc_address=0x7fffffffdfd8) at ../src/gallium/state_trackers/vdpau/device.c:129
#12 0x00007ffff7e6daf5 in vdp_device_create_x11 () from /usr/lib/libvdpau.so.1
#13 0x00005555555554ad in main (argc=<optimized out>, argv=0x7fffffffe168) at vdpauinfo.cpp:488
(gdb) print insn
$1 = (nv50_ir::Instruction *) 0x0
(gdb) # boom! that's guaranteed to blow up yeah...
```
Although there's still a warning, at least the symbol names now look reasonable.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (6 preceding siblings ...)
  2019-07-01 16:34 ` voidlinux-github
@ 2019-07-01 16:49 ` voidlinux-github
  2019-07-02 11:40 ` voidlinux-github
                   ` (4 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-01 16:49 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3521 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507331014
Comment:
Anyway, after installing the `mesa-ati-dri-dbg` package, I get the following backtrace with a bit more detail:
```sh
$ gdb -q vdpauinfo
Reading symbols from vdpauinfo...
Reading symbols from /usr/lib/debug//usr/bin/vdpauinfo...
(gdb) directory /masterdir/builddir/mesa-19.1.1/build
Source directories searched: /masterdir/builddir/mesa-19.1.1/build:$cdir:$cwd
(gdb) set pagination off 
(gdb) run
Starting program: /usr/bin/vdpauinfo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
display: :0   screen: 0
warning: the debug information found in "/usr/lib/vdpau/libvdpau_r300.so.1.0.0" does not match "/usr/lib/vdpau/libvdpau_nouveau.so.1" (CRC mismatch).

[New Thread 0x7fffefbda700 (LWP 23390)]

Thread 1 "vdpauinfo" received signal SIGSEGV, Segmentation fault.
nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590)
    at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
2085	   if (insn->saturate ||
(gdb) bt
#0  nv50_ir::AlgebraicOpt::handleCVT_CVT (this=<optimized out>, cvt=0x555555802590) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2085
#1  0x00007ffff72c1696 in nv50_ir::AlgebraicOpt::visit (this=0x7fffffffc140, bb=<optimized out>) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:2351
#2  0x00007ffff7288210 in nv50_ir::Pass::doRun (this=0x7fffffffc140, func=<optimized out>, ordered=<optimized out>, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_bb.cpp:500
#3  0x00007ffff72882bf in nv50_ir::Pass::doRun (this=0x7fffffffc140, prog=<optimized out>, ordered=false, skipPhi=false) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_inlines.h:413
#4  0x00007ffff72b0deb in nv50_ir::Program::optimizeSSA (this=this@entry=0x5555557ecdb0, level=3) at ../src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp:4005
#5  0x00007ffff72859b7 in nv50_ir_generate_code (info=info@entry=0x5555558440b0) at ../src/gallium/drivers/nouveau/codegen/nv50_ir.cpp:1267
#6  0x00007ffff72ddceb in nvc0_program_translate (prog=prog@entry=0x55555582b5a0, chipset=<optimized out>, debug=debug@entry=0x5555557e7798) at ../src/gallium/drivers/nouveau/nvc0/nvc0_program.c:638
#7  0x00007ffff72e5dac in nvc0_cp_state_create (pipe=0x5555557e73d0, cso=0x7fffffffce20) at ../src/gallium/drivers/nouveau/nvc0/nvc0_context.h:292
#8  0x00007ffff70034f3 in vl_compositor_cs_create_shader (c=c@entry=0x5555557c18b8, compute_shader_text=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor_cs.c:433
#9  0x00007ffff6ffcf2a in init_shaders (c=0x5555557c18b8) at ../src/gallium/auxiliary/vl/vl_compositor.c:74
#10 vl_compositor_init (c=c@entry=0x5555557c18b8, pipe=<optimized out>) at ../src/gallium/auxiliary/vl/vl_compositor.c:767
#11 0x00007ffff6fecdcb in vdp_imp_device_create_x11 (display=<optimized out>, screen=<optimized out>, device=0x7fffffffe03c, get_proc_address=0x7fffffffdfd8) at ../src/gallium/state_trackers/vdpau/device.c:129
#12 0x00007ffff7e6daf5 in vdp_device_create_x11 () from /usr/lib/libvdpau.so.1
#13 0x00005555555554ad in main (argc=<optimized out>, argv=0x7fffffffe168) at vdpauinfo.cpp:488
(gdb) print insn
$1 = (nv50_ir::Instruction *) 0x0
(gdb) # boom! that's guaranteed to blow up yeah...
```
Although there's still a warning, at least the symbol names now look reasonable.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (7 preceding siblings ...)
  2019-07-01 16:49 ` voidlinux-github
@ 2019-07-02 11:40 ` voidlinux-github
  2019-07-02 11:43 ` voidlinux-github
                   ` (3 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-02 11:40 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file by `${wrksrc}/bin/install_megadrivers.py`.

For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so`, all eventually pointing to `libvdpau_gallium.so.1.0.0`. It appears that `xbps-src`'s `common/hooks/post-install/06-strip-and-debug-pkgs.sh` doesn't handle these correctly.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (8 preceding siblings ...)
  2019-07-02 11:40 ` voidlinux-github
@ 2019-07-02 11:43 ` voidlinux-github
  2019-07-02 11:45 ` voidlinux-github
                   ` (2 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-02 11:43 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file by `${wrksrc}/bin/install_megadrivers.py`.

For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so.1.0.0`, all eventually pointing to `libvdpau_gallium.so.1.0.0`. It appears that `xbps-src`'s `common/hooks/post-install/06-strip-and-debug-pkgs.sh` doesn't handle these correctly.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (9 preceding siblings ...)
  2019-07-02 11:43 ` voidlinux-github
@ 2019-07-02 11:45 ` voidlinux-github
  2019-10-09 20:51 ` voidlinux-github
  2019-10-09 20:51 ` voidlinux-github
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-07-02 11:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

New comment by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-507165792
Comment:
The problem appears to be with how the build system installs 'megadrivers', i.e. a bunch of filenames all get symlinked to the same master file by `${wrksrc}/bin/install_megadrivers.py`.

For this issue, on my system, this output from `xbps-src install` step seems relevant (full `xbps-src` install log [here](https://gist.github.com/ackalker/8377b789b50ee6e3b17ccb642e040dd1)):
```
Running custom install script '/usr/bin/python3 /builddir/mesa-19.1.1/bin/install_megadrivers.py /builddir/mesa-19.1.1/build/src/gallium/targets/vdpau/libvdpau_gallium.so.1.0.0 lib/vdpau libvdpau_r300.so.1.0.0 libvdpau_r600.so.1.0.0 libvdpau_radeonsi.so.1.0.0 libvdpau_nouveau.so.1.0.0'
```
This results in a bunch of symlinks, including `libvdpau_nouveau.so.1.0.0`, all eventually leading to `libvdpau_gallium.so.1.0.0`. It appears that `xbps-src`'s `common/hooks/post-install/06-strip-and-debug-pkgs.sh` doesn't handle these correctly.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (10 preceding siblings ...)
  2019-07-02 11:45 ` voidlinux-github
@ 2019-10-09 20:51 ` voidlinux-github
  2019-10-09 20:51 ` voidlinux-github
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-10-09 20:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-540189552

Comment:
The fact that these megadrivers get split into different subpackages complicate this...

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
  2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
                   ` (11 preceding siblings ...)
  2019-10-09 20:51 ` voidlinux-github
@ 2019-10-09 20:51 ` voidlinux-github
  12 siblings, 0 replies; 14+ messages in thread
From: voidlinux-github @ 2019-10-09 20:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/issues/12760#issuecomment-540189552

Comment:
The fact that these megadrivers get split into different subpackages complicates this...

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, back to index

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-30 18:16 [ISSUE] mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace voidlinux-github
2019-07-01  8:20 ` voidlinux-github
2019-07-01  8:24 ` voidlinux-github
2019-07-01  8:30 ` voidlinux-github
2019-07-01  8:35 ` voidlinux-github
2019-07-01 16:14 ` voidlinux-github
2019-07-01 16:30 ` voidlinux-github
2019-07-01 16:34 ` voidlinux-github
2019-07-01 16:49 ` voidlinux-github
2019-07-02 11:40 ` voidlinux-github
2019-07-02 11:43 ` voidlinux-github
2019-07-02 11:45 ` voidlinux-github
2019-10-09 20:51 ` voidlinux-github
2019-10-09 20:51 ` voidlinux-github

Github messages for voidlinux

Archives are clonable: git clone --mirror http://inbox.vuxu.org/voidlinux-github

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.github.voidlinux


AGPL code for this site: git clone https://public-inbox.org/ public-inbox