https://sourceware.org/bugzilla/show_bug.cgi?id=34097
--- Comment #9 from Mark Wielaard <mark at klomp dot org> --- (In reply to Vitaly Chikunov from comment #8) > I think the intent of our use of --strip-all is to maximize binary size > reduction. OK, but does it actually do that? It seems, at least for eu-strip, it is a noop, so it does less stripping than if you give it -g. > If we do -g *globally* just to workaround the bug this will be suboptimal > and would increase sizes of binaries and non-debugging packages. Do you happen to have stats? I am still trying to figure out what the intent of --strip-all is. We might want to implement it properly for eu-strip, but I don't fully understand what it is supposed to do. > But we can switch to -g for these particular files of course. > > The file list looks accidental, though. For Linux 6.18 it's just 7 modules > in drivers/mtd/tests (which I disabled with CONFIG_MTD_TESTS=n). But for > 6.12 it's also lib/crypto/libcurve25519.ko and I am unsure (yet) it will not > appear in the other files on another build. O, that is interesting. So it actually works fine on most .ko files? Do you happen to see a difference between these files? Could you maybe attach a "working" one? Maybe a pre-6.12 libcurve25519.ko that works and a 6.12 libcurve25519.ko that doesn't? > From -f I'd expect that debugging with gdb continues to work seamlessly. If > double .symtab does not break it then it's ok with me. yeah, that should still work. But I am not sure that really is the solution. I think I am missing some detail that I don't fully understand yet. -- You are receiving this mail because: You are on the CC list for the bug.
