From 56ec51a012c76670d421fe9d3d3699278564cee5 Mon Sep 17 00:00:00 2001
From: Justus Winter <4winter@informatik.uni-hamburg.de>
Date: Thu, 15 Aug 2013 09:38:06 +0200
Subject: exec: keep track of the range where executable segments are mapped

Keep track of the range where executable segments are mapped into
memory and hand that information over to the proc server.

* exec/priv.h (struct execdata): Add {start,end}_code.
* exec/exec.c (prepare): Initialize {start,end}_code.
(load_section): Update {start,end}_code.
(do_exec): Use proc_set_code to hand {start,end}_code to the proc server.
---
 exec/priv.h | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'exec/priv.h')

diff --git a/exec/priv.h b/exec/priv.h
index b9c6e990..85e03aee 100644
--- a/exec/priv.h
+++ b/exec/priv.h
@@ -73,6 +73,10 @@ struct execdata
     vm_address_t entry;
     file_t file;
 
+    /* Set by load_section.  */
+    vm_address_t start_code;
+    vm_address_t end_code;
+
     /* Note that if `file_data' (below) is set, then these just point
        into that and should not be deallocated (file_data is malloc'd).  */
     char *map_buffer;		/* Our mapping window or read buffer.  */
-- 
cgit v1.2.3