Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: mesa-nouveau-dri: -dbg package: debug information mismatch, missing details in backtrace
Date: Mon, 01 Jul 2019 18:49:51 +0200	[thread overview]
Message-ID: <20190701164951.TKClTJqre2d0kq6BC3taloDSFFBtai4VMKF4maws0wY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12760@inbox.vuxu.org>

[-- 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.

  parent reply	other threads:[~2019-07-01 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-30 18:16 [ISSUE] " 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 [this message]
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
2019-10-27 10:50 ` voidlinux-github
2019-10-27 10:53 ` voidlinux-github
2019-12-29 16:24 ` voidlinux-github
2019-12-29 16:29 ` [ISSUE] [CLOSED] " voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190701164951.TKClTJqre2d0kq6BC3taloDSFFBtai4VMKF4maws0wY@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).