New: Link BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY to BR2_ENABLE_DEBUG

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

Bug ID: 9441
Summary: Link BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY to
BR2_ENABLE_DEBUG
Product: buildroot
Version: 2015.08
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: blf_sn at yahoo.fr
CC: buildroot at uclibc.org
Target Milestone: ---

Dear all,
What do thing you about enabling BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY when BR2_ENABLE_DEBUG is selected? Or create a submenu for BR2_ENABLE_DEBUG ( build packages with debugging symbols) and setBR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY as a submenu element of BR2_ENABLE_DEBUG.

Very often, I enable BR2_ENABLE_DEBUG and forgot to select BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY because there are not in the same menus. I suppose, may be wrongly, I am not the only one to make that mistake. Best Regards!
Birahim

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

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

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Thomas Petazzoni <[email protected]> --- 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.