aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2021-09-01 15:33:19 +0100
committerAndrew Burgess <aburgess@redhat.com>2021-11-30 12:10:33 +0000
commit0e3b7c25eea80717638617ebafac611ed970def8 (patch)
tree65eaac6eb07c906b3c18903ede558ea8138ad830 /gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp
parentabfdb09f011ac7c76321843d9d0b395ca96e3fef (diff)
downloadgdb-0e3b7c25eea80717638617ebafac611ed970def8.zip
gdb-0e3b7c25eea80717638617ebafac611ed970def8.tar.gz
gdb-0e3b7c25eea80717638617ebafac611ed970def8.tar.bz2
gdb/python: introduce gdb.TargetConnection object type
This commit adds a new object type gdb.TargetConnection. This new type represents a connection within GDB (a connection as displayed by 'info connections'). There's three ways to find a gdb.TargetConnection, there's a new 'gdb.connections()' function, which returns a list of all currently active connections. Or you can read the new 'connection' property on the gdb.Inferior object type, this contains the connection for that inferior (or None if the inferior has no connection, for example, it is exited). Finally, there's a new gdb.events.connection_removed event registry, this emits a new gdb.ConnectionEvent whenever a connection is removed from GDB (this can happen when all inferiors using a connection exit, though this is not always the case, depending on the connection type). The gdb.ConnectionEvent has a 'connection' property, which is the gdb.TargetConnection being removed from GDB. The gdb.TargetConnection has an 'is_valid()' method. A connection object becomes invalid when the underlying connection is removed from GDB (as discussed above, this might be when all inferiors using a connection exit, or it might be when the user explicitly replaces a connection in GDB by issuing another 'target' command). The gdb.TargetConnection has the following read-only properties: 'num': The number for this connection, 'type': e.g. 'native', 'remote', 'sim', etc 'description': The longer description as seen in the 'info connections' command output. 'details': A string or None. Extra details for the connection, for example, a remote connection's details might be 'hostname:port'.
Diffstat (limited to 'gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp')
-rw-r--r--gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp38
1 files changed, 38 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp b/gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp
index 3fd6b15..3f74a47 100644
--- a/gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp
+++ b/gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp
@@ -15,18 +15,27 @@
# Test "info inferiors" and "info connections" with multiple targets.
+load_lib gdb-python.exp
+
source $srcdir/$subdir/multi-target.exp.tcl
if {![multi_target_prepare]} {
return
}
+# Cache the result of calling skip_python_tests into a local variable.
+set run_python_tests [expr ! [skip_python_tests]]
+
# Test "info inferiors" and "info connections". MULTI_PROCESS
# indicates whether the multi-process feature of remote targets is
# turned off or on.
proc test_info_inferiors {multi_process} {
setup "off"
+ if { $::run_python_tests } {
+ gdb_test_no_output "source ${::remote_python_file}" "load python file"
+ }
+
gdb_test_no_output \
"set remote multiprocess-feature-packet $multi_process"
@@ -86,6 +95,18 @@ proc test_info_inferiors {multi_process} {
"[connection_num 5 $inf]${ws}core${ws}Local core dump file${ws}" \
]
+ if { $::run_python_tests } {
+ gdb_test "python info_connections()" \
+ [multi_line \
+ "Num${ws}What${ws}Description" \
+ "[connection_num 1 $inf]${ws}native${ws}Native process" \
+ "[connection_num 2 $inf]${ws}extended-remote localhost:$decimal${ws}Extended remote serial target in gdb-specific protocol" \
+ "[connection_num 3 $inf]${ws}core${ws}Local core dump file" \
+ "[connection_num 4 $inf]${ws}extended-remote localhost:$decimal${ws}Extended remote serial target in gdb-specific protocol" \
+ "[connection_num 5 $inf]${ws}core${ws}Local core dump file" \
+ ]
+ }
+
gdb_test "info inferiors" \
[multi_line \
"Num${ws}Description${ws}Connection${ws}Executable${ws}" \
@@ -96,10 +117,27 @@ proc test_info_inferiors {multi_process} {
"[inf_desc 5 $inf]4 \\(extended-remote localhost:$decimal\\)${ws}${binfile}${ws}" \
"[inf_desc 6 $inf]5 \\(core\\)${ws}${binfile}${ws}" \
]
+
+ if { $::run_python_tests } {
+ gdb_test "python info_inferiors()" \
+ [multi_line \
+ "Inferior 1, Connection #1: native" \
+ "Inferior 2, Connection #2: extended-remote localhost:$decimal" \
+ "Inferior 3, Connection #3: core" \
+ "Inferior 4, Connection #1: native" \
+ "Inferior 5, Connection #4: extended-remote localhost:$decimal" \
+ "Inferior 6, Connection #5: core" \
+ ]
+ }
}
}
}
+if { $run_python_tests } {
+ set remote_python_file [gdb_remote_download host \
+ ${srcdir}/${subdir}/${testfile}.py]
+}
+
# Test "info inferiors" and "info connections" commands.
with_test_prefix "info-inferiors" {
foreach_with_prefix multi_process {"on" "off"} {