Fix build failure in varobj.c:update_dynamic_varobj_children...
authorJoel Brobecker <brobecker@gnat.com>
Tue, 9 Apr 2013 23:30:50 +0000 (23:30 +0000)
committerJoel Brobecker <brobecker@gnat.com>
Tue, 9 Apr 2013 23:30:50 +0000 (23:30 +0000)
... when !HAVE_PYTHON.

gdb/ChangeLog:

        * varobj.c (update_dynamic_varobj_children) [!HAVE_PYTHON]:
        Use gdb_assert_not_reached instead of invalid boolean expression.

gdb/ChangeLog
gdb/varobj.c

index 21aebc323fa8ff7790ca17b4234c4aca8cde358e..f9c7068b8a48a3ee4dfa6ea6de45cb719ff15f9b 100644 (file)
@@ -1,3 +1,8 @@
+2013-04-09  Joel Brobecker  <brobecker@adacore.com>
+
+       * varobj.c (update_dynamic_varobj_children) [!HAVE_PYTHON]:
+       Use gdb_assert_not_reached instead of invalid boolean expression.
+
 2013-04-09  Pedro Alves  <palves@redhat.com>
 
        * remote.c (unpush_and_perror): New function.
index 84588364e2189d9d11455ddd3d8f81b47279bbba..467e59ae0b3163bbc85ddb621676c29fde169cd1 100644 (file)
@@ -1252,7 +1252,7 @@ update_dynamic_varobj_children (struct varobj *var,
 
   return 1;
 #else
-  gdb_assert (0 && "should never be called if Python is not enabled");
+  gdb_assert_not_reached ("should never be called if Python is not enabled");
 #endif
 }
 
This page took 0.053205 seconds and 4 git commands to generate.