Use field_signed from Python MI commands
If an MI command written in Python includes a number in its output, currently that is simply emitted as a string. However, it's convenient for a later patch if these are emitted using field_signed. This does not make a difference to ordinary MI clients.
This commit is contained in:
parent
6aebb6e100
commit
d5ad08d77c
2 changed files with 17 additions and 0 deletions
|
@ -110,6 +110,7 @@
|
|||
typedef PY_LONG_LONG gdb_py_longest;
|
||||
typedef unsigned PY_LONG_LONG gdb_py_ulongest;
|
||||
#define gdb_py_long_as_ulongest PyLong_AsUnsignedLongLong
|
||||
#define gdb_py_long_as_long_and_overflow PyLong_AsLongLongAndOverflow
|
||||
|
||||
#else /* HAVE_LONG_LONG */
|
||||
|
||||
|
@ -118,6 +119,7 @@ typedef unsigned PY_LONG_LONG gdb_py_ulongest;
|
|||
typedef long gdb_py_longest;
|
||||
typedef unsigned long gdb_py_ulongest;
|
||||
#define gdb_py_long_as_ulongest PyLong_AsUnsignedLong
|
||||
#define gdb_py_long_as_long_and_overflow PyLong_AsLongAndOverflow
|
||||
|
||||
#endif /* HAVE_LONG_LONG */
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue