aboutsummaryrefslogtreecommitdiff
path: root/gdb/target-connection.c
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/target-connection.c
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/target-connection.c')
-rw-r--r--gdb/target-connection.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/target-connection.c b/gdb/target-connection.c
index a649423..da1c9da 100644
--- a/gdb/target-connection.c
+++ b/gdb/target-connection.c
@@ -24,6 +24,7 @@
#include "inferior.h"
#include "target.h"
+#include "observable.h"
/* A map between connection number and representative process_stratum
target. */
@@ -49,6 +50,9 @@ connection_list_add (process_stratum_target *t)
void
connection_list_remove (process_stratum_target *t)
{
+ /* Notify about the connection being removed before we reset the
+ connection number to zero. */
+ gdb::observers::connection_removed.notify (t);
process_targets.erase (t->connection_number);
t->connection_number = 0;
}