This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 4/4] py-unwind-maint.exp: Allow unwinders to be called during python import
- From: Pedro Alves <palves at redhat dot com>
- To: Kevin Buettner <kevin at buettner dot to>, gdb-patches at sourceware dot org
- Date: Wed, 12 Oct 2016 14:10:35 +0100
- Subject: Re: [PATCH 4/4] py-unwind-maint.exp: Allow unwinders to be called during python import
- Authentication-results: sourceware.org; auth=none
- References: <20160928014455.438266a2@pinnacle.lan> <20160928015938.2e0b2461@pinnacle.lan>
On 09/28/2016 09:59 AM, Kevin Buettner wrote:
> py-unwind-maint.exp: Allow unwinders to be called during python import
Looks like you have the subject here again.
>
> In his commit of "Fix PR19927: Avoid unwinder recursion if sniffer
> uses calls parse_and_eval", Pedro updated the py-unwind-maint.exp
> test to account for different behavior in GDB caused by his changes
> to frame.c.
>
> This patch changes py-unwind-maint.exp so that either behavior is
> acceptable.
>
> Regardless of which path is taken, the number of PASSes and the
> names of the tests are the same.
I'd like to understand better the need for this.
BTW, should probably use gdb_test_multiple instead
of send_gdb/gdb_expect.
Thanks,
Pedro Alves