From 974eac9d7694ca14dcdf6d1a74777a265fffdb95 Mon Sep 17 00:00:00 2001 From: Ulrich Weigand Date: Tue, 1 Dec 2015 18:04:39 +0100 Subject: [PATCH] Avoid "operation may be undefined" warning in remote.c 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 | 5 +++++ gdb/remote.c | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 49ba2bc8112..2f870918d21 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2015-12-01 Ulrich Weigand + + * remote.c (remote_parse_stop_reply): Avoid GCC 4.1 "operation + may be undefined" warning. + 2015-12-01 Ulrich Weigand * remote.c (remote_newthread_step): Initialize item.name. diff --git a/gdb/remote.c b/gdb/remote.c index c60f173632f..52c5df84c41 100644 --- a/gdb/remote.c +++ b/gdb/remote.c @@ -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. */ -- 2.30.2