All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Hajnoczi <stefanha@redhat.com>, Olaf Hering <olaf@aepfle.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Stefan Weil <sw@weilnetz.de>,
	Cole Robinson <crobinso@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] build: preserve debug symbols with --enable-debug-info
Date: Thu, 25 Sep 2014 15:05:06 +0400	[thread overview]
Message-ID: <5423F6E2.4080801@msgid.tls.msk.ru> (raw)
In-Reply-To: <20140925104954.GE19882@stefanha-thinkpad.redhat.com>

25.09.2014 14:49, Stefan Hajnoczi wrote:
[]
> Perhaps package maintainers rely on installed binaries not having debug
> symbols?

Package maintainer can and _should_ watch for changes in new releases
and update their packages to accomodate changes made upstream.

> It's common to split the debug symbols into separate ELF files that are
> shipped in a different package (qemu-debuginfo or similar).

We was thinking about shipping these in debian (currently we don't
build with debug info enabled), but it turned out to be rather problematic
due to amount of binaries and size of the symbols.  I still consider
enabling debug info for at least x86 system targets (as most widely
used).  Either way, in debian we strip executables outside of upstream
build system usually.

> If you make this change and packagers are unaware, they could
> accidentally ship qemu packages that contain the full debug symbols in
> the binaries.

And it will be their problem entirely, especially if they wont notice
the size difference :)  No, really, this is not something an upstream
should think too much about.

Thanks,

/mjt

  parent reply	other threads:[~2014-09-25 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  8:06 [Qemu-devel] [PATCH] build: preserve debug symbols with --enable-debug-info Olaf Hering
2014-09-25 10:36 ` Peter Maydell
2014-09-25 10:47   ` Olaf Hering
2014-09-25 10:51     ` Peter Maydell
2014-09-25 10:49 ` Stefan Hajnoczi
2014-09-25 10:55   ` Olaf Hering
2014-09-25 11:05   ` Michael Tokarev [this message]
2014-09-25 13:51   ` Paolo Bonzini
2014-10-02 15:39     ` Stefan Hajnoczi

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=5423F6E2.4080801@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=crobinso@redhat.com \
    --cc=olaf@aepfle.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.