Re: [PATCH] gdb/python: fix 'exited' event when GDB exits from core file debugging

[Andrew Burgess <aburgess@redhat.com>]

Lancelot SIX <Lancelot.Six@amd.com> writes:

> Hi Andrew,
>
> Thanks for the quick turnaround!
>
> FYI, when applying the patch, git reports:
>
> ```
> Applying: gdb/python: fix 'exited' event when GDB exits from core file 
> debugging
> .git/rebase-apply/patch:127: indent with spaces.
>              "python print(str(gdb.selected_inferior()))" ""]
> .git/rebase-apply/patch:133: indent with spaces.
>             set inferior_string $expect_out(1,string)
> .git/rebase-apply/patch:134: indent with spaces.
>             incr event_count
> .git/rebase-apply/patch:135: indent with spaces.
>             exp_continue
> .git/rebase-apply/patch:139: indent with spaces.
>             verbose -log "GDB has now exited"
> warning: squelched 7 whitespace errors
> warning: 12 lines add whitespace errors.
> ```

This seems odd, I checked my local patch and I'm pretty sure that these
lines are using tabs then spaces, and the email I sent also appears to
be using tabs as far as I can tell.

I sent a V2 patch, if you are still seeing this issue there then please
let me know and I can try to figure out what's gone wrong.

>
> I expect you could have GDB create the coredump instead of relying on 
> the kernel for this.  This allows this test to run on systems where 
> kernel.core_pattern is not set in a way supported by the testsuite:
>

I took this advice for V2, thank you for the suggestion.

Thanks,
Andrew