invalid string offset for section `.strtab'
See original GitHub issueWhen connecting GEF to the decompiler, gdb fails to add-symbol-file and throws an error.
BFD: /tmp/tmp3pmay68f.c.debug: invalid string offset 16777215 >= 282 for section '.strtab'
Although this does not break decomp2gef, it causes the debugger to be without a symbol file and hence renders some features unusable.
Sample binary with this behavior: sample_program.zip
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
ld: invalid string offset ... for section `.strtab' - Stack Overflow
There was a bug in ld.bfd prior to Binutils 2.33 . It tried to read ARM CMSE symbol names, but used .strtab instead...
Read more >raspberry pi - invalid string offset for section `.strtab' during make
I have tried amd64/i386 platform build on debian Stretch. Clean install without any backports. The latest Samba 4.10.1 builds without any issues ...
Read more >BFD .. invalid string offset .. for section `.strtab' - NetBSD
To: netbsd-users <netbsd-users%netbsd.org@localhost>, current-users <current-users%netbsd.org@localhost> · Subject: BFD .. invalid string offset ...
Read more >1392845 – arm: ld terminated with signal 11 - Red Hat Bugzilla
[exec] /usr/bin/ld: target/sqlite-3.15.1-Linux-arm/NativeDB.o: invalid string offset 65539 >= 4717 for section `.strtab' [exec] /usr/bin/ld: ...
Read more >[Solved]-ld: invalid string offset ... for section `.strtab'-C++
It tried to read ARM CMSE symbol names, but used .strtab instead of .dynstr . If symbols are stripped in a shared library,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Without full triage, I think this may be related to #15. Will resolve #15 first then circle back to this.
closed by #21