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'.
2021-09-01 15:33:19 +01:00
|
|
|
/* Python interface to inferiors.
|
|
|
|
|
|
2026-01-05 08:13:29 -07:00
|
|
|
Copyright (C) 2009-2026 Free Software Foundation, Inc.
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
|
|
|
|
This file is part of GDB.
|
|
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
|
the Free Software Foundation; either version 3 of the License, or
|
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>. */
|
|
|
|
|
|
|
|
|
|
#include "python-internal.h"
|
|
|
|
|
#include "process-stratum-target.h"
|
|
|
|
|
#include "inferior.h"
|
|
|
|
|
#include "observable.h"
|
|
|
|
|
#include "target-connection.h"
|
|
|
|
|
#include "py-events.h"
|
|
|
|
|
#include "py-event.h"
|
|
|
|
|
#include "arch-utils.h"
|
2021-08-31 14:04:36 +01:00
|
|
|
#include "remote.h"
|
|
|
|
|
#include "charset.h"
|
2025-02-25 12:01:21 -07:00
|
|
|
#include "gdbsupport/unordered_map.h"
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
|
|
|
|
/* The Python object that represents a connection. */
|
|
|
|
|
|
2025-10-25 23:55:29 +01:00
|
|
|
struct connection_object : public PyObject
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
{
|
|
|
|
|
/* The process target that represents this connection. When a
|
|
|
|
|
connection_object is created this field will always point at a valid
|
|
|
|
|
target. Later, if GDB stops using this target (the target is popped
|
|
|
|
|
from all target stacks) then this field is set to nullptr, which
|
|
|
|
|
indicates that this Python object is now in the invalid state (see
|
|
|
|
|
the is_valid() method below). */
|
|
|
|
|
struct process_stratum_target *target;
|
|
|
|
|
};
|
|
|
|
|
|
gdb/python: add type traits check for all PyObject sub-classes
All of our custom Python types are created as structs, like this:
struct some_new_type : public PyObject
{
... various fields ...
};
Then instances of this struct are created by calling PyObject_New,
either directly within GDB's C++ code, or within Python when a user's
Python script creates an instance of that class.
The problem is that Python is written in C, and PyObject_New doesn't
call any constructors for `some_new_type`, nor for any of the fields
within `some_new_type`.
If `some_new_type` is Plain Old Data (POD), then this is fine. Or, to
be more C++ specific, if `some_new_type` is trivially default
constructable, then we're fine.
But if a field within `some_new_type` has a non-trivial constructor,
then we're in trouble as that constructor will never be run.
An example of a problematic field type is frame_info_ptr. The
constructor for this type registers the new object with a central
management object, recording the `this` pointer, using this type within
`some_new_type` will not work as expected; frame invalidation will not
show up within the frame_info_ptr as you might expect.
And so, this type trait exists. Whenever a struct is created to define
a new Python type we should add a line like:
static_assert (gdb::is_python_allocatable_v<some_new_type>);
This will fail if any field of `some_new_type` are unsuitable for this
use.
We don't actually check is_trivially_default_constructible here. Some
types, e.g. ui_file_style::color, have non-trivial (or no default)
constructors, but are still safe to use within `some_new_type` because
their constructors just initialise data fields; there's nothing
"special" that the constructor does that cannot be achieved by
assigning the fields after creation with PyObject_New.
What actually matters is that the type is trivially destructible
(Python won't call C++ destructors, so destructors with side effects,
like deregistering from a list, would be skipped) and trivially
copyable (Python may copy objects with memcpy). Types like
frame_info_ptr, whose constructors and destructors have side effects
such as registering with a central management object, will be caught
because they are neither trivially destructible nor trivially copyable.
Simple POD types like ui_file_style are trivially destructible and
copyable, so pass this trait.
This commit adds the new type trait, and makes use of it in all cases
but one, pending_frame_object in python/py-unwind.c, has a field of
type frame_info_ptr, which is currently broken. This will be fixed,
and the static_assert added, in the next commit.
Approved-By: Tom Tromey <tom@tromey.com>
2026-05-14 09:39:57 +01:00
|
|
|
static_assert (gdb::is_python_allocatable_v<connection_object>);
|
|
|
|
|
|
2025-10-21 10:00:20 -06:00
|
|
|
extern PyTypeObject connection_object_type;
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
2025-10-21 10:00:20 -06:00
|
|
|
extern PyTypeObject remote_connection_object_type;
|
2021-08-31 14:04:36 +01:00
|
|
|
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
/* Require that CONNECTION be valid. */
|
|
|
|
|
#define CONNPY_REQUIRE_VALID(connection) \
|
|
|
|
|
do { \
|
|
|
|
|
if (connection->target == nullptr) \
|
|
|
|
|
{ \
|
|
|
|
|
PyErr_SetString (PyExc_RuntimeError, \
|
|
|
|
|
_("Connection no longer exists.")); \
|
|
|
|
|
return nullptr; \
|
|
|
|
|
} \
|
|
|
|
|
} while (0)
|
|
|
|
|
|
|
|
|
|
/* A map between process_stratum targets and the Python object representing
|
|
|
|
|
them. We actually hold a gdbpy_ref around the Python object so that
|
|
|
|
|
reference counts are handled correctly when entries are deleted. */
|
2025-02-25 12:01:21 -07:00
|
|
|
static gdb::unordered_map<process_stratum_target *,
|
|
|
|
|
gdbpy_ref<connection_object>> all_connection_objects;
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
|
|
|
|
/* Return a reference to a gdb.TargetConnection object for TARGET. If
|
|
|
|
|
TARGET is nullptr then a reference to None is returned.
|
|
|
|
|
|
|
|
|
|
Previously created gdb.TargetConnection objects are cached, and
|
|
|
|
|
additional references to the same connection object can be returned with
|
|
|
|
|
later calls to this function. */
|
|
|
|
|
|
|
|
|
|
gdbpy_ref<>
|
|
|
|
|
target_to_connection_object (process_stratum_target *target)
|
|
|
|
|
{
|
|
|
|
|
if (target == nullptr)
|
2026-05-15 21:38:12 +02:00
|
|
|
return py_none ();
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
|
|
|
|
gdbpy_ref <connection_object> conn_obj;
|
|
|
|
|
auto conn_obj_iter = all_connection_objects.find (target);
|
|
|
|
|
if (conn_obj_iter == all_connection_objects.end ())
|
|
|
|
|
{
|
2021-08-31 14:04:36 +01:00
|
|
|
PyTypeObject *type;
|
|
|
|
|
|
|
|
|
|
if (is_remote_target (target))
|
|
|
|
|
type = &remote_connection_object_type;
|
|
|
|
|
else
|
|
|
|
|
type = &connection_object_type;
|
|
|
|
|
|
|
|
|
|
conn_obj.reset (PyObject_New (connection_object, type));
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
if (conn_obj == nullptr)
|
|
|
|
|
return nullptr;
|
|
|
|
|
conn_obj->target = target;
|
|
|
|
|
all_connection_objects.emplace (target, conn_obj);
|
|
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
conn_obj = conn_obj_iter->second;
|
|
|
|
|
|
|
|
|
|
gdb_assert (conn_obj != nullptr);
|
|
|
|
|
|
|
|
|
|
/* Repackage the result as a PyObject reference. */
|
2026-02-21 12:07:37 -07:00
|
|
|
return conn_obj;
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Return a list of gdb.TargetConnection objects, one for each currently
|
|
|
|
|
active connection. The returned list is in no particular order. */
|
|
|
|
|
|
|
|
|
|
PyObject *
|
|
|
|
|
gdbpy_connections (PyObject *self, PyObject *args)
|
|
|
|
|
{
|
|
|
|
|
gdbpy_ref<> list (PyList_New (0));
|
|
|
|
|
if (list == nullptr)
|
|
|
|
|
return nullptr;
|
|
|
|
|
|
|
|
|
|
for (process_stratum_target *target : all_non_exited_process_targets ())
|
|
|
|
|
{
|
|
|
|
|
gdb_assert (target != nullptr);
|
|
|
|
|
|
|
|
|
|
gdbpy_ref<> conn = target_to_connection_object (target);
|
|
|
|
|
if (conn == nullptr)
|
|
|
|
|
return nullptr;
|
|
|
|
|
gdb_assert (conn.get () != Py_None);
|
|
|
|
|
|
|
|
|
|
if (PyList_Append (list.get (), conn.get ()) < 0)
|
|
|
|
|
return nullptr;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return list.release ();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Emit a connection event for TARGET to REGISTRY. Return 0 on success, or
|
|
|
|
|
a negative value on error. */
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
emit_connection_event (process_stratum_target *target,
|
|
|
|
|
eventregistry_object *registry)
|
|
|
|
|
{
|
|
|
|
|
gdbpy_ref<> event_obj
|
|
|
|
|
= create_event_object (&connection_event_object_type);
|
|
|
|
|
if (event_obj == nullptr)
|
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
|
|
gdbpy_ref<> conn = target_to_connection_object (target);
|
|
|
|
|
if (evpy_add_attribute (event_obj.get (), "connection", conn.get ()) < 0)
|
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
|
|
return evpy_emit_event (event_obj.get (), registry);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Callback for the connection_removed observer. */
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
connpy_connection_removed (process_stratum_target *target)
|
|
|
|
|
{
|
|
|
|
|
if (!gdb_python_initialized)
|
|
|
|
|
return;
|
|
|
|
|
|
Change how Python architecture and language are handled
Currently, gdb's Python layer captures the current architecture and
language when "entering" Python code. This has some undesirable
effects, and so this series changes how this is handled.
First, there is code like this:
gdbpy_enter enter_py (python_gdbarch, python_language);
This is incorrect, because both of these are NULL when not otherwise
assigned. This can cause crashes in some cases -- I've added one to
the test suite. (Note that this crasher is just an example, other
ones along the same lines are possible.)
Second, when the language is captured in this way, it means that
Python code cannot affect the current language for its own purposes.
It's reasonable to want to write code like this:
gdb.execute('set language mumble')
... stuff using the current language
gdb.execute('set language previous-value')
However, this won't actually work, because the language is captured on
entry. I've added a test to show this as well.
This patch changes gdb to try to avoid capturing the current values.
The Python concept of the current gdbarch is only set in those few
cases where a non-default value is computed or needed; and the
language is not captured at all -- instead, in the cases where it's
required, the current language is temporarily changed.
2022-01-04 08:02:24 -07:00
|
|
|
gdbpy_enter enter_py;
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
|
|
|
|
if (!evregpy_no_listeners_p (gdb_py_events.connection_removed))
|
|
|
|
|
if (emit_connection_event (target, gdb_py_events.connection_removed) < 0)
|
|
|
|
|
gdbpy_print_stack ();
|
|
|
|
|
|
|
|
|
|
auto conn_obj_iter = all_connection_objects.find (target);
|
|
|
|
|
if (conn_obj_iter != all_connection_objects.end ())
|
|
|
|
|
{
|
|
|
|
|
gdbpy_ref <connection_object> conn_obj = conn_obj_iter->second;
|
|
|
|
|
conn_obj->target = nullptr;
|
|
|
|
|
all_connection_objects.erase (target);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Called when a gdb.TargetConnection object is deallocated. */
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
connpy_connection_dealloc (PyObject *obj)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn_obj = (connection_object *) obj;
|
|
|
|
|
|
|
|
|
|
/* As the all_connection_objects map holds a reference to each connection
|
|
|
|
|
object we can only enter the dealloc function when the reference in
|
|
|
|
|
all_connection_objects has been erased.
|
|
|
|
|
|
|
|
|
|
As we always set the target pointer back to nullptr before we erase
|
|
|
|
|
items from all_connection_objects then, when we get here, the target
|
|
|
|
|
pointer must be nullptr. */
|
|
|
|
|
gdb_assert (conn_obj->target == nullptr);
|
|
|
|
|
|
|
|
|
|
Py_TYPE (obj)->tp_free (obj);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Implement repr() for gdb.TargetConnection. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_repr (PyObject *obj)
|
|
|
|
|
{
|
|
|
|
|
connection_object *self = (connection_object *) obj;
|
|
|
|
|
process_stratum_target *target = self->target;
|
|
|
|
|
|
|
|
|
|
if (target == nullptr)
|
2024-01-04 10:07:48 +00:00
|
|
|
return gdb_py_invalid_object_repr (obj);
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
2022-03-21 10:07:41 -04:00
|
|
|
return PyUnicode_FromFormat ("<%s num=%d, what=\"%s\">",
|
2026-05-26 11:46:29 +01:00
|
|
|
gdbpy_py_obj_tp_name (obj).c_str (),
|
2022-03-21 10:07:41 -04:00
|
|
|
target->connection_number,
|
|
|
|
|
make_target_connection_string (target).c_str ());
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Implementation of gdb.TargetConnection.is_valid() -> Boolean. Returns
|
|
|
|
|
True if this connection object is still associated with a
|
|
|
|
|
process_stratum_target, otherwise, returns False. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_is_valid (PyObject *self, PyObject *args)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn = (connection_object *) self;
|
|
|
|
|
|
|
|
|
|
if (conn->target == nullptr)
|
2026-05-15 21:38:12 +02:00
|
|
|
return py_false ().release ();
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
|
2026-05-15 21:38:12 +02:00
|
|
|
return py_true ().release ();
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Return the id number of this connection. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_get_connection_num (PyObject *self, void *closure)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn = (connection_object *) self;
|
|
|
|
|
|
|
|
|
|
CONNPY_REQUIRE_VALID (conn);
|
|
|
|
|
|
|
|
|
|
auto num = conn->target->connection_number;
|
|
|
|
|
return gdb_py_object_from_longest (num).release ();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Return a string that gives the short name for this connection type. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_get_connection_type (PyObject *self, void *closure)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn = (connection_object *) self;
|
|
|
|
|
|
|
|
|
|
CONNPY_REQUIRE_VALID (conn);
|
|
|
|
|
|
|
|
|
|
const char *shortname = conn->target->shortname ();
|
|
|
|
|
return host_string_to_python_string (shortname).release ();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Return a string that gives a longer description of this connection type. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_get_description (PyObject *self, void *closure)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn = (connection_object *) self;
|
|
|
|
|
|
|
|
|
|
CONNPY_REQUIRE_VALID (conn);
|
|
|
|
|
|
|
|
|
|
const char *longname = conn->target->longname ();
|
|
|
|
|
return host_string_to_python_string (longname).release ();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Return a string that gives additional details about this connection, or
|
|
|
|
|
None, if there are no additional details for this connection type. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_get_connection_details (PyObject *self, void *closure)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn = (connection_object *) self;
|
|
|
|
|
|
|
|
|
|
CONNPY_REQUIRE_VALID (conn);
|
|
|
|
|
|
|
|
|
|
const char *details = conn->target->connection_string ();
|
|
|
|
|
if (details != nullptr)
|
|
|
|
|
return host_string_to_python_string (details).release ();
|
|
|
|
|
else
|
2026-05-15 21:38:12 +02:00
|
|
|
return py_none ().release ();
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Python specific initialization for this file. */
|
|
|
|
|
|
2025-10-21 10:00:20 -06:00
|
|
|
static int
|
|
|
|
|
gdbpy_initialize_connection ()
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
{
|
2024-09-11 10:35:20 -06:00
|
|
|
if (gdbpy_type_ready (&connection_object_type) < 0)
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
return -1;
|
|
|
|
|
|
2024-09-11 10:35:20 -06:00
|
|
|
if (gdbpy_type_ready (&remote_connection_object_type) < 0)
|
2021-08-31 14:04:36 +01:00
|
|
|
return -1;
|
|
|
|
|
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2021-08-31 14:04:36 +01:00
|
|
|
/* Set of callbacks used to implement gdb.send_packet. */
|
|
|
|
|
|
|
|
|
|
struct py_send_packet_callbacks : public send_remote_packet_callbacks
|
|
|
|
|
{
|
|
|
|
|
/* Constructor, initialise the result to nullptr. It is invalid to try
|
|
|
|
|
and read the result before sending a packet and processing the
|
|
|
|
|
reply. */
|
|
|
|
|
|
|
|
|
|
py_send_packet_callbacks ()
|
|
|
|
|
: m_result (nullptr)
|
|
|
|
|
{ /* Nothing. */ }
|
|
|
|
|
|
|
|
|
|
/* There's nothing to do when the packet is sent. */
|
|
|
|
|
|
|
|
|
|
void sending (gdb::array_view<const char> &buf) override
|
|
|
|
|
{ /* Nothing. */ }
|
|
|
|
|
|
|
|
|
|
/* When the result is returned create a Python object and assign this
|
|
|
|
|
into M_RESULT. If for any reason we can't create a Python object to
|
|
|
|
|
represent the result then M_RESULT is set to nullptr, and Python's
|
|
|
|
|
internal error flags will be set. If the result we got back from the
|
|
|
|
|
remote is empty then set the result to None. */
|
|
|
|
|
|
|
|
|
|
void received (gdb::array_view<const char> &buf) override
|
|
|
|
|
{
|
|
|
|
|
if (buf.size () > 0 && buf.data ()[0] != '\0')
|
|
|
|
|
m_result.reset (PyBytes_FromStringAndSize (buf.data (), buf.size ()));
|
|
|
|
|
else
|
|
|
|
|
{
|
|
|
|
|
/* We didn't get back any result data; set the result to None. */
|
2026-05-15 21:38:12 +02:00
|
|
|
m_result = py_none ();
|
2021-08-31 14:04:36 +01:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Get a reference to the result as a Python object. It is invalid to
|
|
|
|
|
call this before sending a packet to the remote and processing the
|
|
|
|
|
reply.
|
|
|
|
|
|
|
|
|
|
The result value is setup in the RECEIVED call above. If the RECEIVED
|
|
|
|
|
call causes an error then the result value will be set to nullptr,
|
|
|
|
|
and the error reason is left stored in Python's global error state.
|
|
|
|
|
|
|
|
|
|
It is important that the result is inspected immediately after sending
|
|
|
|
|
a packet to the remote, and any error fetched, calling any other
|
|
|
|
|
Python functions that might clear the error state, or rely on an error
|
2024-11-23 12:20:34 +01:00
|
|
|
not being set will cause undefined behavior. */
|
2021-08-31 14:04:36 +01:00
|
|
|
|
|
|
|
|
gdbpy_ref<> result () const
|
|
|
|
|
{
|
|
|
|
|
return m_result;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
private:
|
|
|
|
|
|
|
|
|
|
/* A reference to the result value. */
|
|
|
|
|
|
|
|
|
|
gdbpy_ref<> m_result;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* Implement RemoteTargetConnection.send_packet function. Send a packet to
|
|
|
|
|
the target identified by SELF. The connection must still be valid, and
|
|
|
|
|
the packet to be sent must be non-empty, otherwise an exception will be
|
|
|
|
|
thrown. */
|
|
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
|
connpy_send_packet (PyObject *self, PyObject *args, PyObject *kw)
|
|
|
|
|
{
|
|
|
|
|
connection_object *conn = (connection_object *) self;
|
|
|
|
|
|
|
|
|
|
CONNPY_REQUIRE_VALID (conn);
|
|
|
|
|
|
|
|
|
|
static const char *keywords[] = {"packet", nullptr};
|
|
|
|
|
PyObject *packet_obj;
|
|
|
|
|
|
|
|
|
|
if (!gdb_PyArg_ParseTupleAndKeywords (args, kw, "O", keywords,
|
|
|
|
|
&packet_obj))
|
|
|
|
|
return nullptr;
|
|
|
|
|
|
|
|
|
|
/* If the packet is a unicode string then convert it to a bytes object. */
|
|
|
|
|
if (PyUnicode_Check (packet_obj))
|
|
|
|
|
{
|
|
|
|
|
/* We encode the string to bytes using the ascii codec, if this fails
|
|
|
|
|
then a suitable error will have been set. */
|
|
|
|
|
packet_obj = PyUnicode_AsASCIIString (packet_obj);
|
|
|
|
|
if (packet_obj == nullptr)
|
|
|
|
|
return nullptr;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Check the packet is now a bytes object. */
|
|
|
|
|
if (!PyBytes_Check (packet_obj))
|
|
|
|
|
{
|
|
|
|
|
PyErr_SetString (PyExc_TypeError, _("Packet is not a bytes object"));
|
|
|
|
|
return nullptr;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
Py_ssize_t packet_len = 0;
|
|
|
|
|
char *packet_str_nonconst = nullptr;
|
|
|
|
|
if (PyBytes_AsStringAndSize (packet_obj, &packet_str_nonconst,
|
|
|
|
|
&packet_len) < 0)
|
|
|
|
|
return nullptr;
|
|
|
|
|
const char *packet_str = packet_str_nonconst;
|
|
|
|
|
gdb_assert (packet_str != nullptr);
|
|
|
|
|
|
|
|
|
|
if (packet_len == 0)
|
|
|
|
|
{
|
|
|
|
|
PyErr_SetString (PyExc_ValueError, _("Packet must not be empty"));
|
|
|
|
|
return nullptr;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
try
|
|
|
|
|
{
|
|
|
|
|
scoped_restore_current_thread restore_thread;
|
|
|
|
|
switch_to_target_no_thread (conn->target);
|
|
|
|
|
|
|
|
|
|
gdb::array_view<const char> view (packet_str, packet_len);
|
|
|
|
|
py_send_packet_callbacks callbacks;
|
|
|
|
|
send_remote_packet (view, &callbacks);
|
|
|
|
|
PyObject *result = callbacks.result ().release ();
|
|
|
|
|
/* If we encountered an error converting the reply to a Python
|
|
|
|
|
object, then the result here can be nullptr. In that case, Python
|
|
|
|
|
should be aware that an error occurred. */
|
|
|
|
|
gdb_assert ((result == nullptr) == (PyErr_Occurred () != nullptr));
|
|
|
|
|
return result;
|
|
|
|
|
}
|
|
|
|
|
catch (const gdb_exception &except)
|
|
|
|
|
{
|
2024-09-24 13:06:32 +02:00
|
|
|
return gdbpy_handle_gdb_exception (nullptr, except);
|
2021-08-31 14:04:36 +01:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
/* Global initialization for this file. */
|
|
|
|
|
|
2025-05-22 11:54:16 -06:00
|
|
|
INIT_GDB_FILE (py_connection)
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
{
|
|
|
|
|
gdb::observers::connection_removed.attach (connpy_connection_removed,
|
|
|
|
|
"py-connection");
|
|
|
|
|
}
|
|
|
|
|
|
gdb/python: add mechanism to manage Python initialization functions
Currently, when we add a new python sub-system to GDB,
e.g. py-inferior.c, we end up having to create a new function like
gdbpy_initialize_inferior, which then has to be called from the
function do_start_initialization in python.c.
In some cases (py-micmd.c and py-tui.c), we have two functions
gdbpy_initialize_*, and gdbpy_finalize_*, with the second being called
from finalize_python which is also in python.c.
This commit proposes a mechanism to manage these initialization and
finalization calls, this means that adding a new Python subsystem will
no longer require changes to python.c or python-internal.h, instead,
the initialization and finalization functions will be registered
directly from the sub-system file, e.g. py-inferior.c, or py-micmd.c.
The initialization and finalization functions are managed through a
new class gdbpy_initialize_file in python-internal.h. This class
contains a single global vector of all the initialization and
finalization functions.
In each Python sub-system we create a new gdbpy_initialize_file
object, the object constructor takes care of registering the two
callback functions.
Now from python.c we can call static functions on the
gdbpy_initialize_file class which take care of walking the callback
list and invoking each callback in turn.
To slightly simplify the Python sub-system files I added a new macro
GDBPY_INITIALIZE_FILE, which hides the need to create an object. We
can now just do this:
GDBPY_INITIALIZE_FILE (gdbpy_initialize_registers);
One possible problem with this change is that there is now no
guaranteed ordering of how the various sub-systems are initialized (or
finalized). To try and avoid dependencies creeping in I have added a
use of the environment variable GDB_REVERSE_INIT_FUNCTIONS, this is
the same environment variable used in the generated init.c file.
Just like with init.c, when this environment variable is set we
reverse the list of Python initialization (and finalization)
functions. As there is already a test that starts GDB with the
environment variable set then this should offer some level of
protection against dependencies creeping in - though for full
protection I guess we'd need to run all gdb.python/*.exp tests with
the variable set.
I have tested this patch with the environment variable set, and saw no
regressions, so I think we are fine right now.
One other change of note was for gdbpy_initialize_gdb_readline, this
function previously returned void. In order to make this function
have the correct signature I've updated its return type to int, and we
now return 0 to indicate success.
All of the other initialize (and finalize) functions have been made
static within their respective sub-system files.
There should be no user visible changes after this commit.
2022-09-16 16:08:17 +01:00
|
|
|
GDBPY_INITIALIZE_FILE (gdbpy_initialize_connection);
|
|
|
|
|
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
/* Methods for the gdb.TargetConnection object type. */
|
|
|
|
|
|
|
|
|
|
static PyMethodDef connection_object_methods[] =
|
|
|
|
|
{
|
|
|
|
|
{ "is_valid", connpy_is_valid, METH_NOARGS,
|
|
|
|
|
"is_valid () -> Boolean.\n\
|
|
|
|
|
Return true if this TargetConnection is valid, false if not." },
|
|
|
|
|
{ NULL }
|
|
|
|
|
};
|
|
|
|
|
|
2021-08-31 14:04:36 +01:00
|
|
|
/* Methods for the gdb.RemoteTargetConnection object type. */
|
|
|
|
|
|
|
|
|
|
static PyMethodDef remote_connection_object_methods[] =
|
|
|
|
|
{
|
|
|
|
|
{ "send_packet", (PyCFunction) connpy_send_packet,
|
|
|
|
|
METH_VARARGS | METH_KEYWORDS,
|
|
|
|
|
"send_packet (PACKET) -> Bytes\n\
|
|
|
|
|
Send PACKET to a remote target, return the reply as a bytes array." },
|
|
|
|
|
{ NULL }
|
|
|
|
|
};
|
|
|
|
|
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
/* Attributes for the gdb.TargetConnection object type. */
|
|
|
|
|
|
|
|
|
|
static gdb_PyGetSetDef connection_object_getset[] =
|
|
|
|
|
{
|
|
|
|
|
{ "num", connpy_get_connection_num, NULL,
|
|
|
|
|
"ID number of this connection, as assigned by GDB.", NULL },
|
|
|
|
|
{ "type", connpy_get_connection_type, NULL,
|
|
|
|
|
"A short string that is the name for this connection type.", NULL },
|
|
|
|
|
{ "description", connpy_get_description, NULL,
|
|
|
|
|
"A longer string describing this connection type.", NULL },
|
|
|
|
|
{ "details", connpy_get_connection_details, NULL,
|
|
|
|
|
"A string containing additional connection details.", NULL },
|
|
|
|
|
{ NULL }
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* Define the gdb.TargetConnection object type. */
|
|
|
|
|
|
|
|
|
|
PyTypeObject connection_object_type =
|
|
|
|
|
{
|
|
|
|
|
PyVarObject_HEAD_INIT (NULL, 0)
|
|
|
|
|
"gdb.TargetConnection", /* tp_name */
|
|
|
|
|
sizeof (connection_object), /* tp_basicsize */
|
|
|
|
|
0, /* tp_itemsize */
|
|
|
|
|
connpy_connection_dealloc, /* tp_dealloc */
|
|
|
|
|
0, /* tp_print */
|
|
|
|
|
0, /* tp_getattr */
|
|
|
|
|
0, /* tp_setattr */
|
|
|
|
|
0, /* tp_compare */
|
|
|
|
|
connpy_repr, /* tp_repr */
|
|
|
|
|
0, /* tp_as_number */
|
|
|
|
|
0, /* tp_as_sequence */
|
|
|
|
|
0, /* tp_as_mapping */
|
|
|
|
|
0, /* tp_hash */
|
|
|
|
|
0, /* tp_call */
|
|
|
|
|
0, /* tp_str */
|
|
|
|
|
0, /* tp_getattro */
|
|
|
|
|
0, /* tp_setattro */
|
|
|
|
|
0, /* tp_as_buffer */
|
2021-08-31 14:04:36 +01:00
|
|
|
Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE, /* tp_flags */
|
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'.
2021-09-01 15:33:19 +01:00
|
|
|
"GDB target connection object", /* tp_doc */
|
|
|
|
|
0, /* tp_traverse */
|
|
|
|
|
0, /* tp_clear */
|
|
|
|
|
0, /* tp_richcompare */
|
|
|
|
|
0, /* tp_weaklistoffset */
|
|
|
|
|
0, /* tp_iter */
|
|
|
|
|
0, /* tp_iternext */
|
|
|
|
|
connection_object_methods, /* tp_methods */
|
|
|
|
|
0, /* tp_members */
|
|
|
|
|
connection_object_getset, /* tp_getset */
|
|
|
|
|
0, /* tp_base */
|
|
|
|
|
0, /* tp_dict */
|
|
|
|
|
0, /* tp_descr_get */
|
|
|
|
|
0, /* tp_descr_set */
|
|
|
|
|
0, /* tp_dictoffset */
|
|
|
|
|
0, /* tp_init */
|
|
|
|
|
0 /* tp_alloc */
|
|
|
|
|
};
|
2021-08-31 14:04:36 +01:00
|
|
|
|
|
|
|
|
/* Define the gdb.RemoteTargetConnection object type. */
|
|
|
|
|
|
|
|
|
|
PyTypeObject remote_connection_object_type =
|
|
|
|
|
{
|
|
|
|
|
PyVarObject_HEAD_INIT (NULL, 0)
|
|
|
|
|
"gdb.RemoteTargetConnection", /* tp_name */
|
|
|
|
|
sizeof (connection_object), /* tp_basicsize */
|
|
|
|
|
0, /* tp_itemsize */
|
|
|
|
|
connpy_connection_dealloc, /* tp_dealloc */
|
|
|
|
|
0, /* tp_print */
|
|
|
|
|
0, /* tp_getattr */
|
|
|
|
|
0, /* tp_setattr */
|
|
|
|
|
0, /* tp_compare */
|
|
|
|
|
connpy_repr, /* tp_repr */
|
|
|
|
|
0, /* tp_as_number */
|
|
|
|
|
0, /* tp_as_sequence */
|
|
|
|
|
0, /* tp_as_mapping */
|
|
|
|
|
0, /* tp_hash */
|
|
|
|
|
0, /* tp_call */
|
|
|
|
|
0, /* tp_str */
|
|
|
|
|
0, /* tp_getattro */
|
|
|
|
|
0, /* tp_setattro */
|
|
|
|
|
0, /* tp_as_buffer */
|
|
|
|
|
Py_TPFLAGS_DEFAULT, /* tp_flags */
|
|
|
|
|
"GDB remote target connection object", /* tp_doc */
|
|
|
|
|
0, /* tp_traverse */
|
|
|
|
|
0, /* tp_clear */
|
|
|
|
|
0, /* tp_richcompare */
|
|
|
|
|
0, /* tp_weaklistoffset */
|
|
|
|
|
0, /* tp_iter */
|
|
|
|
|
0, /* tp_iternext */
|
|
|
|
|
remote_connection_object_methods, /* tp_methods */
|
|
|
|
|
0, /* tp_members */
|
|
|
|
|
0, /* tp_getset */
|
|
|
|
|
&connection_object_type, /* tp_base */
|
|
|
|
|
0, /* tp_dict */
|
|
|
|
|
0, /* tp_descr_get */
|
|
|
|
|
0, /* tp_descr_set */
|
|
|
|
|
0, /* tp_dictoffset */
|
|
|
|
|
0, /* tp_init */
|
|
|
|
|
0 /* tp_alloc */
|
|
|
|
|
};
|