From: Nicolas Blanc <nicolas.blanc@intel.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org, Nicolas Blanc <nicolas.blanc@intel.com>
Subject: [PATCH v17 4/5] Function is_elf_target.
Date: Fri, 18 Oct 2013 13:40:00 -0000 [thread overview]
Message-ID: <1382103635-15300-5-git-send-email-nicolas.blanc@intel.com> (raw)
In-Reply-To: <1382103635-15300-1-git-send-email-nicolas.blanc@intel.com>
2013-27-09 Nicolas Blanc <nicolas.blanc@intel.com>
gdb/testsuite
* lib/gdb.exp (is_elf_target): New function.
Signed-off-by: Nicolas Blanc <nicolas.blanc@intel.com>
---
gdb/testsuite/lib/gdb.exp | 39 +++++++++++++++++++++++++++++++++++++++
1 files changed, 39 insertions(+), 0 deletions(-)
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 44786ec..1b51d7a 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -1796,6 +1796,45 @@ proc supports_reverse {} {
return 0
}
+# Return 1 if target is ELF.
+gdb_caching_proc is_elf_target {
+ set me "is_elf_target"
+
+ set src [standard_temp_file is_elf_target[pid].c]
+ set obj [standard_temp_file is_elf_target[pid].o]
+
+ set fp_src [open $src "w"]
+ puts $fp_src "int foo () {return 0;}"
+ close $fp_src
+
+ verbose "$me: compiling testfile $src" 2
+ set lines [gdb_compile $src $obj object {quiet}]
+
+ file delete $src
+
+ if ![string match "" $lines] then {
+ verbose "$me: testfile compilation failed, returning 0" 2
+ return 0
+ }
+
+ set fp_obj [open $obj "r"]
+ fconfigure $fp_obj -translation binary
+ set data [read $fp_obj]
+ close $fp_obj
+
+ file delete $obj
+
+ set ELFMAG "\u007FELF"
+
+ if {[string compare -length 4 $data $ELFMAG] != 0} {
+ verbose "$me: returning 0" 2
+ return 0
+ }
+
+ verbose "$me: returning 1" 2
+ return 1
+}
+
# Return 1 if target is ILP32.
# This cannot be decided simply from looking at the target string,
# as it might depend on externally passed compiler options like -m64.
--
1.7.6.5
next prev parent reply other threads:[~2013-10-18 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 13:40 [PATCH v17 0/5] remove-symbol-file & add-symbol-file Nicolas Blanc
2013-10-18 13:40 ` Nicolas Blanc [this message]
2013-10-18 13:40 ` [PATCH v17 5/5] Test adding and removing a symbol file at runtime Nicolas Blanc
2013-10-18 13:41 ` [PATCH v17 3/5] Create target sections for user-added symbol files Nicolas Blanc
2013-10-18 13:41 ` [PATCH v17 2/5] Documentation for the remove-symbol-file command Nicolas Blanc
2013-10-18 13:41 ` [PATCH v17 1/5] New " Nicolas Blanc
2013-10-24 19:44 ` [PATCH v17 0/5] remove-symbol-file & add-symbol-file Tom Tromey
2013-10-29 11:06 ` Blanc, Nicolas
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=1382103635-15300-5-git-send-email-nicolas.blanc@intel.com \
--to=nicolas.blanc@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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).