search for: 00c300

...t; color[(x>=0.004)&(x<0.005)]<-"#00FE00" color[(x>=0.005)&(x<0.006)]<-"#00F700" color[(x>=0.006)&(x<0.007)]<-"#00E400" color[(x>=0.007)&(x<0.008)]<-"#00D600" color[(x>=0.008)&(x<0.009)]<-"#00C300" and so on but I don't like to do it manually... do know a solution... Thank you very much chris [[alternative HTML version deleted]]

...e are the numbers for a fresh built CLANG in Debug mode on Ubuntu 20.04 using GCC 10.2: $ readelf -SW clang-12 | grep debug | awk '{print $2, $6}' | column -t .debug_aranges 00c240 .debug_info 34d1fd .debug_abbrev 00841f .debug_line 023093 .debug_str 53685f .debug_ranges 00c300 As you can see, ".debug_str" is visibly bigger than ".debug_info". Of course, CLANG does not suffer from DWARF32 limits. This is just a relatively large project, which anyone can easily check by themselves. -- Best Regards, Igor Kudrin C++ Developer, Access Softek, Inc.​

On 18.11.2020 0:20, Robinson, Paul wrote: > This is a problem only if the .debug_str section *by itself* exceeds 4GB; > are we anticipating that will happen IRL? The section is just a string > section, by itself it has no 32/64 format. > > If the .debug_str section *by itself* exceeds 4GB, then yes any string > with a 32-bit reference to it must be in the first 4GB. Strings