This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/2] Fix PR breakpoints/16889: gdb segfaults when printing ASM SDT arguments
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Fri, 02 May 2014 17:57:00 -0300
- Subject: Re: [PATCH 1/2] Fix PR breakpoints/16889: gdb segfaults when printing ASM SDT arguments
- Authentication-results: sourceware.org; auth=none
- References: <1398981131-11720-1-git-send-email-sergiodj at redhat dot com> <1398981131-11720-2-git-send-email-sergiodj at redhat dot com> <53636901 dot 9090601 at redhat dot com> <m3lhuk40pm dot fsf at redhat dot com> <m3oazg2gys dot fsf at redhat dot com> <5363EA5A dot 1000209 at redhat dot com>
On Friday, May 02 2014, Pedro Alves wrote:
> FYI, with {} instead of [list ...] one can avoid the backslashes.
> That is, one can write:
>
> foreach probe_name {foo bar foo_prefix bar_prefix} \
> probe_val {42 42 42 42} \
> probe_reg_val {"$rsp" "$rbp - 8" "$rsp" "$rbp - 8"} {
>
> instead of:
>
> foreach probe_name [list "foo" "bar" "foo_prefix" "bar_prefix"] \
> probe_val [list "42" "42" "42" "42"] \
> probe_reg_val [list "\$rsp" "\$rbp - 8" "\$rsp" "\$rbp - 8"] {
> with_test_prefix $probe_name {
>
> Just a suggestion, it doesn't matter at all.
Thanks for the suggestion. I actually knew about it, but believe it or
not I prefer to use [list ...] instead of { } in this case, because I
think it is more elegant. Go figure...
Anyway, pushed:
<https://sourceware.org/ml/gdb-cvs/2014-05/msg00004.html>
Thanks,
--
Sergio