Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9441] Link BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY to BR2_ENABLE_DEBUG
Date: Wed, 12 Jul 2017 07:54:31 +0000	[thread overview]
Message-ID: <bug-9441-163-UMlLEheacM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9441-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9441

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
While I understand your reasoning, I don't think we want to do that. Indeed,
some people like you need debugging symbols to use with gdbserver on the
target. But there are lots of other use cases for building with debugging
symbols:

 - Using the full blown gdb directly on the target
 - Using tools like objdump/readelf on the host, without necessarily needing
gdbserver on the target

Hence, I don't think we want to tie building with debugging symbols with having
gdbserver copied to the target.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2017-07-12  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21  9:43 [Buildroot] [Bug 9441] New: Link BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY to BR2_ENABLE_DEBUG bugzilla at busybox.net
2017-07-12  7:54 ` bugzilla at busybox.net [this message]

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=bug-9441-163-UMlLEheacM@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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