kill volatile struct gdb_exception
authorPedro Alves <palves@redhat.com>
Sat, 7 Mar 2015 14:50:03 +0000 (14:50 +0000)
committerPedro Alves <palves@redhat.com>
Sat, 7 Mar 2015 15:25:09 +0000 (15:25 +0000)
After the previous patch, this is the last remaining use of a volatile
struct gdb_exception.  Kill it, as it's troublesome for C++: we can't
assign volatile <-> non-volatile without copy constructors /
assignment operators that do that, which I'd rather avoid.

gdb/ChangeLog:
2015-03-07  Pedro Alves  <palves@redhat.com>

* main.c (handle_command_errors): Remove volatile qualifier from
parameter.

gdb/ChangeLog
gdb/main.c

index a18830fc10aed4848e30659cabda498e4605f97b..8f5029a44864a098c316076c2f9f8565988e91cf 100644 (file)
@@ -1,3 +1,8 @@
+2015-03-07  Pedro Alves  <palves@redhat.com>
+
+       * main.c (handle_command_errors): Remove volatile qualifier from
+       parameter.
+
 2015-03-07  Pedro Alves  <palves@redhat.com>
 
        * breakpoint.c (save_breakpoints): Adjust to avoid code between
index ceca80738ef707d537075f5841413285a14ebde9..72b8714eb0056ff7f71abd7bc155c3fc9c5a64c6 100644 (file)
@@ -339,7 +339,7 @@ captured_command_loop (void *data)
    catch_command_errors/catch_command_errors_const.  */
 
 static int
-handle_command_errors (volatile struct gdb_exception e)
+handle_command_errors (struct gdb_exception e)
 {
   if (e.reason < 0)
     {
This page took 0.02956 seconds and 4 git commands to generate.