From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] Make get_frame_langauge take a frame argument
Date: Tue, 04 Aug 2015 15:40:00 -0000 [thread overview]
Message-ID: <cover.1438699523.git.andrew.burgess@embecosm.com> (raw)
This two patch series was a result of looking into getting rid of
deprecated_safe_get_selected_frame. I don't remove the function in
this patch set, in fact I only remove one use, inside
get_frame_langauge, however, I think the change is a good one and can
be pushed regardless of any other work in this area.
The first patch makes get_frame_langauge take a frame parameter,
rather than just operating on the currently selected frame.
The second patch moves get_frame_langauge into frame.c, which I think
is a better place for it. If folk disagree then I'm happy to leave
the function where it is.
Tested on x86-64 Linux only with no regressions.
OK to apply?
Thanks,
Andrew
--
Andrew Burgess (2):
gdb: get_frame_language now takes a frame parameter.
gdb: Move get_frame_language from stack.c to frame.c.
gdb/ChangeLog | 21 +++++++++++++++++++++
gdb/frame.c | 42 ++++++++++++++++++++++++++++++++++++++++++
gdb/frame.h | 6 ++++++
gdb/language.c | 34 ++++++++++++++++++++++++++--------
gdb/language.h | 2 --
gdb/stack.c | 45 ---------------------------------------------
gdb/top.c | 8 +++++---
7 files changed, 100 insertions(+), 58 deletions(-)
--
2.4.0
next reply other threads:[~2015-08-04 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 15:40 Andrew Burgess [this message]
2015-08-04 15:40 ` [PATCH 1/2] gdb: get_frame_language now takes a frame parameter Andrew Burgess
2015-08-04 16:02 ` Pedro Alves
2015-08-07 8:56 ` Andrew Burgess
2015-08-07 9:45 ` Pedro Alves
2015-08-04 15:40 ` [PATCH 2/2] gdb: Move get_frame_language from stack.c to frame.c Andrew Burgess
2015-08-04 16:02 ` Pedro Alves
2015-08-07 8:57 ` Andrew Burgess
2015-08-07 9:45 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1438699523.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox