Github messages for voidlinux
 help / color / mirror / Atom feed
From: fkaa <fkaa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ffmpeg-dbg package doesn't contain debug symbols
Date: Sat, 20 Feb 2021 17:20:24 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28931@inbox.vuxu.org> (raw)

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

New issue by fkaa on void-packages repository

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

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.10.16_1 x86_64 AuthenticAMD notuptodate rrrmdDFFFFFF
* package: ffmpeg-dbg-4.3.1_6


### Expected behavior
FFmpeg binaries (ffmpeg, ffplay, ffprobe) from the ffmpeg-dbg package should contain debug symbols.

### Actual behavior
The binaries from the ffmpeg-dbg package are already stripped. The build process of FFmpeg creates a stripped binary and one with debug symbols with a `_g` suffix. See https://ffmpeg.org/faq.html#Why-are-the-ffmpeg-programs-devoid-of-debugging-symbols_003f for more details.

### Steps to reproduce the behavior
1. Install ffmpeg-dbg
2. Run `gdb ffmpeg` which declares no debug symbols were found


             reply	other threads:[~2021-02-20 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 16:20 fkaa [this message]
2021-02-20 16:46 ` ericonr
2021-02-21 12:20 ` sgn
2021-02-22 23:53 ` [ISSUE] [CLOSED] " sgn

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-28931@inbox.vuxu.org \
    --to=fkaa@users.noreply.github.com \
    --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).