This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [testsuite patch] Fix testsuite regression by: Do not skip prologue for asm (.S) files
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches at sourceware dot org
- Date: Fri, 10 Jul 2015 15:32:39 +0100
- Subject: Re: [testsuite patch] Fix testsuite regression by: Do not skip prologue for asm (.S) files
- Authentication-results: sourceware.org; auth=none
- References: <20150629163708 dot GA28795 at host1 dot jankratochvil dot net> <86lheol7wz dot fsf at gmail dot com> <20150710114743 dot GA12225 at host1 dot jankratochvil dot net>
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> Names of the testcases involved, it was always written this way for whatever
> reason, unless it has changed:
>
> +gdb_test "f" "asmsrc1\[.\]s:$line_enter.*gdbasm_enter" "f at main"
> +
> +# Execute the `n' command.
> +gdb_test "n" "$line_main\[ \]*.*several_nops" "n at main"
I don't know such convention of writing changelog entry for .exp changes.
We usually put the proc or variable name into the parenthesis, like,
* gdb.foo/bar.exp (proc_name): XXXX
Is it documented somewhere?
--
Yao (éå)