https://sourceware.org/bugzilla/show_bug.cgi?id=32271
--- Comment #7 from Stas Sergeev <stsp at users dot sourceforge.net> --- (In reply to Nick Clifton from comment #6) > (In reply to Stas Sergeev from comment #5) > > > Even if it covers some "random" > > data in a file? IMHO that's still > > a but. If it would be zero-sized > > then fine. But its not. > > Can you provide a small example that reproduces this please ? It looks like > something that needs to be investigated. I think you just need to `strip --srip-debug -R '.note.*' tmp.elf` on an attached example. I can't claim anything, because I didn't check where the stalled segment points. But I assume it points to the invalid locations because its sections were removed? Or am I wrong? > My bad. The option is -Ttext-segment=... rather than --text-segment=... > Sorry. Wow! This actually works. So is it the same as just specifying the new load address for all segments? For example if I use -Trodata-segment then not all segments are moved, but -Ttext-segment seems to move them all, including notes. Could you please explain why it is so, or just assure me it will always move all segments? This seems to be all I need. > > Now it hints me to use -text-segment=0x08148000 > > only to declare it "unrecognized option"? > > Very funny. :) > > Yeah - the algorithm for hinting at spelling mistake corrections is not that > smart... Well, for sure it could at least check if such option actually exists, before suggesting. ld.lld (aka llvm ld) does the correct hint. -- You are receiving this mail because: You are on the CC list for the bug.
