Fix uninitialized variable warnings in remote.c
Fix a couple of places where a struct thread_item was added to a vector while the item.name field was uninitialized. gdb/ * remote.c (remote_newthread_step): Initialize item.name. (remote_get_threads_with_qthreadinfo): Likewise.
This commit is contained in:
parent
99fd02d9fc
commit
2e3b657e3a
2 changed files with 7 additions and 0 deletions
|
@ -1,3 +1,8 @@
|
|||
2015-12-01 Ulrich Weigand <uweigand@de.ibm.com>
|
||||
|
||||
* remote.c (remote_newthread_step): Initialize item.name.
|
||||
(remote_get_threads_with_qthreadinfo): Likewise.
|
||||
|
||||
2015-11-30 Pedro Alves <palves@redhat.com>
|
||||
|
||||
PR 14618
|
||||
|
|
|
@ -2914,6 +2914,7 @@ remote_newthread_step (threadref *ref, void *data)
|
|||
|
||||
item.ptid = ptid_build (pid, threadref_to_int (ref), 0);
|
||||
item.core = -1;
|
||||
item.name = NULL;
|
||||
item.extra = NULL;
|
||||
|
||||
VEC_safe_push (thread_item_t, context->items, &item);
|
||||
|
@ -3079,6 +3080,7 @@ remote_get_threads_with_qthreadinfo (struct target_ops *ops,
|
|||
|
||||
item.ptid = read_ptid (bufp, &bufp);
|
||||
item.core = -1;
|
||||
item.name = NULL;
|
||||
item.extra = NULL;
|
||||
|
||||
VEC_safe_push (thread_item_t, context->items, &item);
|
||||
|
|
Loading…
Reference in a new issue