[pushed] gdb/python: prevent conversion from pointer to bool in to_python()
Checks
Commit Message
While converting some Python code to use new "safety" APIs I realized
that calling to_python() with a pointer like (for example):
to_python (symtab->compunit ().objfile ())
calls to_python(bool) which is unlikely to be what the user wants.
This commit changes the code to make it a compile-time error.
After trying several approaches, the least intrusive seemed to be
handling bool specially in to_python() template for integral types and
removing to_python(bool) altogether. This way, the above example fails
with:
error: no matching function for call to ‘to_python(objfile*)’
Tested on x86_64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
---
gdb/python/py-safety.h | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
@@ -71,17 +71,13 @@ namespace safety_details
used in gdb, these are all Python-facing and will return NULL on
error. */
-static inline PyObject *
-to_python (bool value)
-{
- return PyBool_FromLong (value);
-}
-
template<typename T, typename = gdb::Requires<std::is_integral<T>>>
static inline PyObject *
to_python (T value)
{
- if constexpr (std::is_signed<T>::value)
+ if constexpr (std::is_same<T, bool>::value)
+ return PyBool_FromLong (value);
+ else if constexpr (std::is_signed<T>::value)
return gdb_py_object_from_longest (value).release ();
else
return gdb_py_object_from_ulongest (value).release ();