바이너리파일이 32bit용 인지 64bit용 인지 어떻게 확인하죠?
글쓴이: k1d0bus3 / 작성시간: 월, 2016/08/01 - 12:03오후
32bit 시스템에 설치된 부트로더가 32bit용 syslinux인지, 64bit용 syslinux인지 모르겠습니다.
(사실 syslinux가 32bit용, 64bit용 따로 있는지 조차도 모르겠습니다.)
# file ldlinux.sys ldlinux.sys: SYSLINUX loader (version 3.83)
file 명령어도 안통하는데, 어떻게 확인해야 하죠?
Forums:


바이너리가 맞다면... # objdump
바이너리가 맞다면...
소곤소곤
root@ubuntu64:/media/root/ROO
root@ubuntu64:/media/root/ROOT-A/boot/extlinux# objdump -a ldlinux.sys objdump: ldlinux.sys: File format not recognized root@ubuntu64:/media/root/ROOT-A/boot/extlinux# objdump -i ldlinux.sys BFD header file version (GNU Binutils for Ubuntu) 2.24 elf64-x86-64 (header little endian, data little endian) i386 elf32-i386 (header little endian, data little endian) i386 elf32-x86-64 (header little endian, data little endian) i386 a.out-i386-linux (header little endian, data little endian) i386 pei-i386 (header little endian, data little endian) i386 pei-x86-64 (header little endian, data little endian) i386 elf64-l1om (header little endian, data little endian) l1om elf64-k1om (header little endian, data little endian) k1om elf64-little (header little endian, data little endian) i386 l1om k1om plugin elf64-big (header big endian, data big endian) i386 l1om k1om plugin elf32-little (header little endian, data little endian) i386 l1om k1om plugin elf32-big (header big endian, data big endian) i386 l1om k1om plugin pe-x86-64 (header little endian, data little endian) i386 pe-i386 (header little endian, data little endian) i386 plugin (header little endian, data little endian) srec (header endianness unknown, data endianness unknown) i386 l1om k1om plugin symbolsrec (header endianness unknown, data endianness unknown) i386 l1om k1om plugin verilog (header endianness unknown, data endianness unknown) i386 l1om k1om plugin tekhex (header endianness unknown, data endianness unknown) i386 l1om k1om plugin binary (header endianness unknown, data endianness unknown) i386 l1om k1om plugin ihex (header endianness unknown, data endianness unknown) i386 l1om k1om plugin elf64-x86-64 elf32-i386 elf32-x86-64 a.out-i386-linux pei-i386 i386 elf64-x86-64 elf32-i386 elf32-x86-64 a.out-i386-linux pei-i386 l1om ------------ ---------- ------------ ---------------- -------- k1om ------------ ---------- ------------ ---------------- -------- plugin ------------ ---------- ------------ ---------------- -------- pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big i386 pei-x86-64 ---------- ---------- elf64-little elf64-big l1om ---------- elf64-l1om ---------- elf64-little elf64-big k1om ---------- ---------- elf64-k1om elf64-little elf64-big plugin ---------- ---------- ---------- elf64-little elf64-big elf32-little elf32-big pe-x86-64 pe-i386 plugin srec symbolsrec i386 elf32-little elf32-big pe-x86-64 pe-i386 ------ srec symbolsrec l1om elf32-little elf32-big --------- ------- ------ srec symbolsrec k1om elf32-little elf32-big --------- ------- ------ srec symbolsrec plugin elf32-little elf32-big --------- ------- ------ srec symbolsrec verilog tekhex binary ihex i386 verilog tekhex binary ihex l1om verilog tekhex binary ihex k1om verilog tekhex binary ihex plugin verilog tekhex binary ihex어떻게 해석하나요?
바이너리 파일 맞나요? # file -bi
바이너리 파일 맞나요?
소곤소곤
네
이건 단순히 32bit/64bit의 개념이 아니라
이건 단순히 32bit/64bit의 개념이 아니라 bootloader를 설명해주실 분이 필요하겠네요.
혹 제가 답변을 드릴 수 있을까 해서 검색해 봤지만 제 분야와 너무 거리가 멀어졌습니다.
소곤소곤
댓글 달기