This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [obv] compile-print.exp: xfail->kfail for '@' GDB array operator
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Doug Evans <dje at google dot com>
- Cc: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches <gdb-patches at sourceware dot org>, Phil Muldoon <pmuldoon at redhat dot com>
- Date: Fri, 5 Jun 2015 17:26:15 +0200
- Subject: Re: [obv] compile-print.exp: xfail->kfail for '@' GDB array operator
- Authentication-results: sourceware.org; auth=none
- References: <20150604193820 dot GA18453 at host1 dot jankratochvil dot net> <86d21ao5vw dot fsf at gmail dot com> <20150605124035 dot GA1995 at host1 dot jankratochvil dot net> <CADPb22RdmOyA+ryQVmKYMxPpsBRvnkWOnkmS2PQ4F05xa-VShA at mail dot gmail dot com>
On Fri, 05 Jun 2015 17:19:05 +0200, Doug Evans wrote:
> the plan isn't to remove the "standard 'print' command", right?
> [The print (output, etc.) commands would either use the builtin
> support or compile print.]
Sure GCC will probably never become a hard requirement for GDB.
I think there could be:
set compile print never = current state
set compile print always = never use internal GDB evaluation
set compile print preferred = first try GCC then GDB evaluation
- IMO to be the default (as long as GCC is available)
set compile print deferred = first try GDB then GCC evaluation
But the setting above has never been implemented/posted/discussed.
Jan