Test results for commit 46d020960241fcafd7d0ab483746a206829620ea on branch gdb-7.9-branch

[sergiodj at redhat dot com]

*** TEST RESULTS FOR COMMIT 46d020960241fcafd7d0ab483746a206829620ea ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 46d020960241fcafd7d0ab483746a206829620ea

framefilter quit: Code cleanup: Avoid gotos
goto error patters are sometimes AFAIK used in C for the cases like:
	int retval=-1;
	if (!(a=malloc())) goto error;
	if (!(b=malloc())) goto error_a;
	if (!(c=malloc())) goto error_b;
	retval=0;
	error_c: free(c);
	error_b: free(b);
	error_a: free(a);
	error: return retval;

But here there is single error label with one do_cleanups() which I do not find
it worth the goto complication.  Without goto one can then furher merge code in
the exit paths in the next patches and ... after all it is all the same, just
without a goto.

gdb/ChangeLog
2015-02-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* python/py-framefilter.c (py_print_frame): Substitute goto error.
	Remove the error label.