poke-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Poke utility pk-elfextractor


From: Indu Bhagat
Subject: Poke utility pk-elfextractor
Date: Sat, 20 Feb 2021 00:17:44 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1

Hello,

I was trying to use the Poke utility pk-elfextractor and found that perhaps it needs a fix as follows :

diff --git a/utils/pk-elfextractor.in b/utils/pk-elfextractor.in
index adb57b53..669e53b9 100755
--- a/utils/pk-elfextractor.in
+++ b/utils/pk-elfextractor.in
@@ -37,7 +37,7 @@ try

     for (shdr in elf.shdr where shdr.sh_type != 0x0)
       {
-        var sname = elf.get_string (shdr.sh_name);
+        var sname = elf.get_section_name (shdr.sh_name);

         if (section_name == "" || sname == section_name)
           save :ios elf'ios :file file_name + sname


Now, after the fix, I was expecting the output file to be containing only the requested section. However, I am seeing some zero'd out bytes at the beginning of the output files.

Looks like some buffered/zero'd out bytes are being flushed out to the output file. Can someone confirm what is the expected behavior of pk-elfextractor?

$ hexdump -C ctf-enum-1.o.ctf
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000040 f2 df 04 02 00 00 00 00 00 00 00 00 37 00 00 00 |............7...| 00000050 00 00 00 00 00 00 00 00 04 00 00 00 04 00 00 00 |................|

Note how the bytes starting at 0x40 is the CTF magic number (0xdff2).

A perhaps orthogonal problem is that a CTF_Section @ 64#B fails with a "unhandled constraint violation exception". A visual comparison of bytes does not show any problems when compared to the .ctf section from the original object file (ctf-enum-1.o). But I will get to that bridge once I know what to expect from pk-elfextractor.

Thanks
Indu



reply via email to

[Prev in Thread] Current Thread [Next in Thread]