From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: [PATCH 08/14] introduce call_function_by_hand_dummy
Date: Fri, 16 May 2014 15:26:00 -0000 [thread overview]
Message-ID: <1400253995-12333-9-git-send-email-tromey@redhat.com> (raw)
In-Reply-To: <1400253995-12333-1-git-send-email-tromey@redhat.com>
From: Jan Kratochvil <jan.kratochvil@redhat.com>
This provides a variant of call_function_by_hand that allows the dummy
frame destructor to be set. This is used by the compiler code to
manage some resources when calling the gdb-generated inferior
function.
2014-05-16 Jan Kratochvil <jan.kratochvil@redhat.com>
* infcall.h (call_function_by_hand_dummy): Declare.
* infcall.c (call_function_by_hand): Use
call_function_by_hand_dummy.
(call_function_by_hand_dummy): Rename from call_function_by_hand.
Add arguments. Register a destructor.
---
gdb/ChangeLog | 8 ++++++++
gdb/infcall.c | 15 ++++++++++++++-
gdb/infcall.h | 11 +++++++++++
3 files changed, 33 insertions(+), 1 deletion(-)
diff --git a/gdb/infcall.c b/gdb/infcall.c
index 9907263..52a2dae 100644
--- a/gdb/infcall.c
+++ b/gdb/infcall.c
@@ -450,6 +450,14 @@ cleanup_delete_std_terminate_breakpoint (void *ignore)
delete_std_terminate_breakpoint ();
}
+/* See infcall.h. */
+
+struct value *
+call_function_by_hand (struct value *function, int nargs, struct value **args)
+{
+ return call_function_by_hand_dummy (function, nargs, args, NULL, NULL);
+}
+
/* All this stuff with a dummy frame may seem unnecessarily complicated
(why not just save registers in GDB?). The purpose of pushing a dummy
frame which looks just like a real frame is so that if you call a
@@ -469,7 +477,10 @@ cleanup_delete_std_terminate_breakpoint (void *ignore)
ARGS is modified to contain coerced values. */
struct value *
-call_function_by_hand (struct value *function, int nargs, struct value **args)
+call_function_by_hand_dummy (struct value *function,
+ int nargs, struct value **args,
+ call_function_by_hand_dummy_dtor_ftype *dummy_dtor,
+ void *dummy_dtor_data)
{
CORE_ADDR sp;
struct type *values_type, *target_values_type;
@@ -826,6 +837,8 @@ call_function_by_hand (struct value *function, int nargs, struct value **args)
caller (and identify the dummy-frame) onto the dummy-frame
stack. */
dummy_frame_push (caller_state, &dummy_id);
+ if (dummy_dtor != NULL)
+ register_dummy_frame_dtor (dummy_id, dummy_dtor, dummy_dtor_data);
/* Discard both inf_status and caller_state cleanups.
From this point on we explicitly restore the associated state
diff --git a/gdb/infcall.h b/gdb/infcall.h
index c6dcdc3..f895e33 100644
--- a/gdb/infcall.h
+++ b/gdb/infcall.h
@@ -38,4 +38,15 @@ extern CORE_ADDR find_function_addr (struct value *function,
extern struct value *call_function_by_hand (struct value *function, int nargs,
struct value **args);
+/* Similar to call_function_by_hand and additional call
+ register_dummy_frame_dtor with DUMMY_DTOR and DUMMY_DTOR_DATA for the
+ created inferior call dummy frame. */
+
+typedef void (call_function_by_hand_dummy_dtor_ftype) (void *data);
+extern struct value *
+ call_function_by_hand_dummy (struct value *function, int nargs,
+ struct value **args,
+ call_function_by_hand_dummy_dtor_ftype *dummy_dtor,
+ void *dummy_dtor_data);
+
#endif
--
1.9.0
next prev parent reply other threads:[~2014-05-16 15:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 15:26 [PATCH 00/14] let gdb reuse gcc's C compiler Tom Tromey
2014-05-16 15:26 ` [PATCH 03/14] add some missing ops to DWARF assembler Tom Tromey
2014-05-16 15:26 ` [PATCH 10/14] make dwarf_expr_frame_base_1 public Tom Tromey
2014-05-16 15:26 ` [PATCH 07/14] add infcall_mmap and gcc_target_options gdbarch methods Tom Tromey
2014-05-19 6:13 ` Yao Qi
2014-05-19 6:41 ` Jan Kratochvil
2014-05-19 6:47 ` Jan Kratochvil
2014-05-19 7:42 ` Yao Qi
2014-05-19 8:26 ` Agovic, Sanimir
2014-05-19 11:15 ` Jan Kratochvil
2014-05-16 15:26 ` [PATCH 01/14] introduce ui_file_write_for_put Tom Tromey
2014-05-16 15:26 ` Tom Tromey [this message]
2014-05-16 15:26 ` [PATCH 02/14] add gcc/gdb interface files Tom Tromey
2014-05-19 8:06 ` Yao Qi
2014-05-19 13:53 ` Tom Tromey
2014-05-16 15:27 ` [PATCH 14/14] the "compile" command Tom Tromey
2014-06-16 9:55 ` (Doc ping [for news and manual]) -- " Phil Muldoon
2014-06-16 15:25 ` Eli Zaretskii
2014-06-20 9:17 ` Phil Muldoon
2014-06-20 9:42 ` Eli Zaretskii
2014-06-20 10:01 ` Phil Muldoon
2014-06-20 12:37 ` Eli Zaretskii
2014-06-20 14:42 ` Tom Tromey
2014-06-20 19:00 ` Eli Zaretskii
2014-06-21 7:32 ` Eli Zaretskii
2014-05-16 15:41 ` [PATCH 05/14] change how the CLI handles comments Tom Tromey
2014-05-18 23:26 ` Doug Evans
2014-05-19 14:07 ` Phil Muldoon
2014-06-03 7:04 ` Doug Evans
2014-05-16 15:43 ` [PATCH 12/14] add linux_infcall_mmap Tom Tromey
2014-05-16 15:43 ` [PATCH 13/14] add s390_gcc_target_options Tom Tromey
2014-05-16 15:43 ` [PATCH 09/14] split dwarf2_fetch_cfa_info from dwarf2_compile_expr_to_ax Tom Tromey
2014-05-16 15:56 ` [PATCH 04/14] add make_unqualified_type Tom Tromey
2014-05-16 16:18 ` [PATCH 06/14] add dummy frame destructor Tom Tromey
2014-05-16 16:18 ` [PATCH 11/14] export dwarf2_reg_to_regnum_or_error Tom Tromey
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=1400253995-12333-9-git-send-email-tromey@redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).