Oh, and I guess you could always make something even more artificial by
hand - if you compile some random code with -g to assembly, you could then
just pad out a .debug_info contribution with lots of zeros (there are some
assembly directives for that, I think, but don't know assembly that well
off
I /believe/ that Chromium (maybe specifically on ARM? not sure) may have
hit/had problems with the 4GB limit - probably trivially if you build with
clang but pass `-fstandalone-debug` which disables many type
reduction/deduplication strategies.
If you want something more standalone... this:
#def
Is anyone aware of an open-source program or test program that when compiled
and built on Linux x86_64, results in a .debug_info section that is greater
than 4GB? I'm looking for a test program (realistic or not) that contains
32-bit DWARF CUs in a .debug_info section that is about 5GB long, or
