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>
- Cc: gdb-patches at sourceware dot org, Phil Muldoon <pmuldoon at redhat dot com>
- Date: Mon, 27 Apr 2015 18:19:14 +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> <553E5646 dot 8020708 at redhat dot com> <20150427164757 dot GA10548 at host1 dot jankratochvil dot net>
On 04/27/2015 05:47 PM, Jan Kratochvil wrote:
> On Mon, 27 Apr 2015 17:31:18 +0200, Pedro Alves wrote:
>> 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?
>
> Are these questions or directions? I do not have an answer for the questions.
Both. I was curious on the reason why this was added as a flag
to a method, and on your thoughts, because, as I said, I seems to me
that that's not the best direction. So if there's no good reason,
I think it should indeed be made a separate method.
Thanks,
Pedro Alves