Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] stripped .so files in mesa-*-dri-dbg
Date: Sat, 05 Oct 2019 04:17:02 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15104@inbox.vuxu.org> (raw)

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

New issue by blah1 on void-packages repository

https://github.com/void-linux/void-packages/issues/15104

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  `Void 5.2.18_1 x86_64-musl GenuineIntel uptodate rrrnFFFFFF`
* package:  
  `mesa-intel-dri-dbg-19.1.7_3`
possibly also:
  `mesa-ati-dri-dbg-19.1.7_3`
  `mesa-nouveau-dri-dbg-19.1.7_3`
  `mesa-vmwgfx-dri-dbg-19.1.7_3`

### Expected behavior
Using gdb to debug a crash in /usr/lib/xorg/modules/drivers/i915_dri.so shows the relevant functions where the crash occured.
/usr/lib/debug/usr/lib/xorg/modules/i915_dri.so is more than a megabyte in size and not stripped

### Actual behavior
gdb shows "#0  0x00007ffff6d86cd9 in ?? () from /usr/lib/xorg/modules/drivers/i915_dri.so" and similar lines for relevant functions
`file /usr/lib/debug/usr/lib/xorg/modules/drivers/i915_dri.so` says that the file is stripped
`ls -l /usr/lib/debug/usr/lib/xorg/modules/drivers/i915_dri.so` says that the file is only 2768 bytes

### Steps to reproduce the behavior
Run `file /usr/lib/debug/usr/lib/xorg/modules/drivers/i915_dri.so` and see if the file is stripped of debugging symbols
A list of stripped files in mesa-\*-dri-dbg packages can be acquired with `for j in ati nouveau intel vmwgfx ; do xbps-query -f mesa-"$j"-dri-dbg ; done |while read -r i ; do ls -l "$i" ; file "$i" ; done |grep -B1 ', stripped' |grep -v '^--$' |sed '2~2d'`
These are the mesa-*-dri-dbg files that I found that are stripped:
  `/usr/lib/debug/usr/lib/dri/nouveau_drv_video.so`
  `/usr/lib/debug/usr/lib/libXvMCnouveau.so.1.0.0`
  `/usr/lib/debug/usr/lib/vdpau/libvdpau_nouveau.so.1.0.0`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/nouveau_dri.so`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/nouveau_vieux_dri.so`
  `/usr/lib/debug/usr/lib/dri/r600_drv_video.so`
  `/usr/lib/debug/usr/lib/vdpau/libvdpau_r300.so.1.0.0`
  `/usr/lib/debug/usr/lib/vdpau/libvdpau_r600.so.1.0.0`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/r200_dri.so`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/r300_dri.so`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/r600_dri.so`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/i915_dri.so`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/i965_dri.so`
  `/usr/lib/debug/usr/lib/xorg/modules/drivers/vmwgfx_dri.so`
Take this with a grain of salt because I'm a novice at debugging and for all I know some of those are supposed to be stripped.

### Workaround(?)
In testing mesa-ati-dri-dbg for completeness, I found that using gdb to debug the same crash as before gave the message `warning: the debug information found in "/usr/lib/xorg/modules/drivers/radeon_dri.so" does not match "/usr/lib/xorg/modules/drivers/i915_dri.so" (CRC mismatch).`
gdb then gives backtrace lines such as `#0  0x00007ffff6d86cd9 in _mesa_reallocate_registers (prog=prog@entry=0x55555590b230) at ..src/mesa/program/prog_optimize.c:1103`
I don't know if these are the right function names and line numbers exactly, but it seems like installing mesa-ati-dri-dbg is a workaround?

I think my bug still stands, you shouldn't need to install mesa-ati-dri-dbg and mesa-ati-dri in order to debug mesa-intel-dri. It also seems suspicious that a number of debug object files are stripped.

             reply	other threads:[~2019-10-05  2:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05  2:17 voidlinux-github [this message]
2019-10-07 23:20 ` Stripped " voidlinux-github
2019-10-07 23:22 ` voidlinux-github
2019-10-07 23:25 ` voidlinux-github
2019-10-07 23:27 ` voidlinux-github
2019-10-07 23:32 ` voidlinux-github
2019-10-07 23:33 ` voidlinux-github
2019-10-07 23:36 ` voidlinux-github
2019-10-08  8:19 ` voidlinux-github
2019-12-27 22:19 ` voidlinux-github
2019-12-27 22:19 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15104@inbox.vuxu.org \
    --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).