[Bug gdb/31440] [gdb] FAIL: gdb.python/py-progspace-events.exp: inferior 1 (timeout)

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31440

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[gdb/testsuite] FAIL:       |[gdb] FAIL:
                   |gdb.python/py-progspace-eve |gdb.python/py-progspace-eve
                   |nts.exp: inferior 1         |nts.exp: inferior 1
                   |(timeout)                   |(timeout)
          Component|testsuite                   |gdb

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, the test-case says:
...
# Switch to inferior 2 and continue until we hit breakpt.                       
gdb_test "inferior 2" "\\\[Switching to inferior 2 .*"
gdb_continue_to_breakpoint "run to breakpt in inferior 2"

# Let inferior 2 exit.  The new program space is not removed at this            
# point.                                                                        
gdb_test "continue" \
    [multi_line \
         "^Continuing\\." \
         "\\\[Inferior $decimal \[^\r\n\]+ exited normally\\\]"] \
    "continue until inferior 2 exits"

gdb_test "inferior 1" "\\\[Switching to inferior 1 .*"

# Step the inferior.  During this process GDB will prune the now                
# defunct inferior, which deletes its program space, which should               
# trigger the FreeProgspaceEvent.                                               
...

So, it explicitly states that the FreeProgspaceEvent should not happen until
after the step is issued.

At this point I'm not sure if this is indeed a test-case issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.