Bug 9441

Summary:	Link BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY to BR2_ENABLE_DEBUG
Product:	buildroot	Reporter:	Birahim Fall <blf_sn>
Component:	Other	Assignee:	unassigned
Status:	RESOLVED WONTFIX
Severity:	enhancement	CC:	buildroot
Priority:	P5
Version:	2015.08
Target Milestone:	---
Hardware:	PC
OS:	Linux
Host:		Target:
Build:

Description Birahim Fall 2016-11-21 09:43:42 UTC

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

Comment 1 Thomas Petazzoni 2017-07-12 07:54:31 UTC

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.