This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename
- From: Pedro Alves <palves at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org
- Cc: Phil Muldoon <pmuldoon at redhat dot com>
- Date: Mon, 27 Apr 2015 16:31:18 +0100
- Subject: Re: [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename
- Authentication-results: sourceware.org; auth=none
- References: <20150423203402 dot 23140 dot 92757 dot stgit at host1 dot jankratochvil dot net>
On 04/23/2015 09:34 PM, Jan Kratochvil wrote:
> Hi,
>
> in the mail thread
> https://sourceware.org/ml/gdb-patches/2015-04/msg00804.html
> the idea of breaking libcc1.so compatibility was rejected.
>
> Therefore this patch series implements full backward/forward GCC/GDB ABI
> compatibility.
Thanks.
>
> As discussed in
> How to use compile & execute function in GDB
> https://sourceware.org/ml/gdb/2015-04/msg00026.html
>
> GDB currently searches for /usr/bin/ARCH-OS-gcc and chooses one but it does not
> display which one. It cannot, GCC method set_arguments() does not yet know
> whether 'set debug compile' is enabled or not.
>
Hmm, but does it really make sense to add a "verbose" flag to
particular methods incrementally?
It seems to me that "set debug compile" should enable verbosity in
in the plugin, for all methods. Which in turn suggests to me
that we should have a separate method in the plugin for toggling
verbosity?
Thanks,
Pedro Alves