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

[Pedro Alves <pedro@palves.net>]

Hi,

On 2026-06-09 11:19, Andrew Burgess wrote:

> +int
> +main (void)
> +{
> +  alarm (300);

Can you use gdb_watchdog, please?  It'll make this work on Windows too, in theory.
At least, the non-core parts of the tests.

> +# Load the Python script for this test.  Record the string
> +# representation of the current inferior.  Then exit GDB.  Ensure that
> +# during the exit we see a single Python 'exited' event associated
> +# with the expected inferior.
> +proc source_py_script_and_exit_checking_event {} {
> +    gdb_test_no_output "source $::remote_python_file" \
> +	"load python script"
> +
> +    set expected_inferior_string \
> +	[capture_command_output \
> +	     "python print(str(gdb.selected_inferior()))" ""]
> +
> +    set inferior_string ""
> +    set event_count 0
> +    gdb_test_multiple "with confirm off -- exit" "exit gdb" {

...

> +
> +	-re "^\[^\r\n\]*\r\n" {
> +	    exp_continue
> +	}

This looks like could use "-lbl".

Otherwise LGTM.

Approved-by: Pedro Alves <pedro@palves.net>