diff options
author | Jerome Guitton <guitton@adacore.com> | 2017-11-21 14:10:01 -0800 |
---|---|---|
committer | Joel Brobecker <brobecker@adacore.com> | 2017-11-21 14:34:30 -0800 |
commit | 3b1b69bffe522f22d269723856d2caa901041819 (patch) | |
tree | 816a0470eab36a5e3a5c930021f8230366db95de /gdb/ChangeLog-1993 | |
parent | 54aa6c67f5a0d52dabd428cc40ce02781032acd3 (diff) | |
download | fsf-binutils-gdb-3b1b69bffe522f22d269723856d2caa901041819.zip fsf-binutils-gdb-3b1b69bffe522f22d269723856d2caa901041819.tar.gz fsf-binutils-gdb-3b1b69bffe522f22d269723856d2caa901041819.tar.bz2 |
ravenscar: update inferior ptid with event ptid
When debugging a program using a ravenscar runtime, the thread
layer sometimes gets confused, and even missing some threads.
This was traced to an assumption that ravenscar_wait was making,
which is that calling the "to_wait" target_ops method would
set the inferior_ptid, so that we could then use that assumption
to update our thread_list and current ptid. However, this has not
been the case for quite a while now. This patch fixes the problem
by assigning inferior_ptid the ptid returned by "to_wait".
gdb/ChangeLog:
* ravenscar-thread.c (ravenscar_wait): Update inferior ptid
with event ptid from the lower layer before doing the
ravenscar-specific update.
Diffstat (limited to 'gdb/ChangeLog-1993')
0 files changed, 0 insertions, 0 deletions