Avoid "operation may be undefined" warning in remote.c
authorUlrich Weigand <ulrich.weigand@de.ibm.com>
Tue, 1 Dec 2015 17:04:39 +0000 (18:04 +0100)
committerUlrich Weigand <ulrich.weigand@de.ibm.com>
Tue, 1 Dec 2015 17:04:39 +0000 (18:04 +0100)
GCC 4.1 gives the following warning:
gdb/remote.c: In function 'remote_parse_stop_reply':
gdb/remote.c:6549: warning: operation on 'p' may be undefined
on this line of code:

event->ptid = read_ptid (++p, &p);

Since p actually isn't used afterwards anyway, simply use NULL.

gdb/
* remote.c (remote_parse_stop_reply): Avoid GCC 4.1 "operation
may be undefined" warning.

gdb/ChangeLog
gdb/remote.c

index 49ba2bc..2f87091 100644 (file)
@@ -1,5 +1,10 @@
 2015-12-01  Ulrich Weigand  <uweigand@de.ibm.com>
 
+       * remote.c (remote_parse_stop_reply): Avoid GCC 4.1 "operation
+       may be undefined" warning.
+
+2015-12-01  Ulrich Weigand  <uweigand@de.ibm.com>
+
        * remote.c (remote_newthread_step): Initialize item.name.
        (remote_get_threads_with_qthreadinfo): Likewise.
 
index c60f173..52c5df8 100644 (file)
@@ -6548,7 +6548,7 @@ Packet: '%s'\n"),
        event->ws.value.integer = value;
        if (*p != ';')
          error (_("stop reply packet badly formatted: %s"), buf);
-       event->ptid = read_ptid (++p, &p);
+       event->ptid = read_ptid (++p, NULL);
        break;
       }
     case 'W':          /* Target exited.  */