PING: [PATCH 0/2] frame_find_by_id & selected_frame issues

[Andrew Burgess <andrew dot burgess at embecosm dot com>]

Seems that I originally failed to post patch 2/2 from the original
series.  So here's both of them again, rebased on latest master.

I believe that these patches should still be applied even in light of
the discussion here:
  https://sourceware.org/ml/gdb-patches/2015-07/msg00241.html
as any solution that does come out of that conversation will probably
be limited to changing the user interface of gdb, not the underlying
behaviour.  Also that conversation is about future clean up, while
this patch series addresses real, user visible, assertion failures.

--

Andrew Burgess (2):
  gdb: Check the selected-frame in frame_find_by_id.
  gdb: Select a frame for frame_info.

 gdb/ChangeLog                           | 13 ++++++
 gdb/frame.c                             | 39 ++++++++++++++++--
 gdb/frame.h                             |  5 +++
 gdb/stack.c                             | 10 +++++
 gdb/testsuite/ChangeLog                 | 12 ++++++
 gdb/testsuite/gdb.base/create-frame.c   | 34 ++++++++++++++++
 gdb/testsuite/gdb.base/create-frame.exp | 36 +++++++++++++++++
 gdb/testsuite/gdb.mi/mi-var-frame.c     | 34 ++++++++++++++++
 gdb/testsuite/gdb.mi/mi-var-frame.exp   | 70 +++++++++++++++++++++++++++++++++
 9 files changed, 250 insertions(+), 3 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/create-frame.c
 create mode 100644 gdb/testsuite/gdb.base/create-frame.exp
 create mode 100644 gdb/testsuite/gdb.mi/mi-var-frame.c
 create mode 100644 gdb/testsuite/gdb.mi/mi-var-frame.exp

-- 
2.4.0