search for: at_range

...Right - use one reloc and then offsets for the rest I suppose. Seems like a reasonable feature but one we're basically not using at all (just not "not using correctly"). As usual, I'd be inclined to rip it out until it's used (until we actually emit the non-reloc, offset-based AT_range values), but not too fussed. > It's not necessarily fission only, but it hasn't been standardized yet > and is a bit of an experiment and still undergoing revision. I can > disable it/command line if you think that's appropriate as well. Doesn't seem terribly necessary -...

It looks like we only attach the GNU_ranges_base to skeleton CUs, and never use the attribute under non-fission. Is that right? It's not obvious to me why we'd want to only include this under fission, but I admittedly don't fully understand it anyway. - Dave

On Mon, Dec 9, 2013 at 9:47 AM, David Blaikie <dblaikie at gmail.com> wrote: > It looks like we only attach the GNU_ranges_base to skeleton CUs, and > never use the attribute under non-fission. Is that right? It's not > obvious to me why we'd want to only include this under fission, but I > admittedly don't fully understand it anyway. > So we're not

...dbghelp: Add support for stream lookup by name in PDB files and use it for strings stream. dbghelp: Get stream indexes out of PDB files (instead of hardwired values). dbghelp: When failing to look up for a PDB file, don't keep a module format object around. dbghelp: Use AT_range attribute (for function, block... addresses) when AT_low_pc and AT_high_pc are not present. dbghelp, winedump: Added definition for S_FRAMEPROC_V2 symbol (CodeView). kernel32: Added support for terminfo/termcap in console code. kernel32: Move the input character to INPUT_RECORD tr...