[Lldb-commits] [PATCH] Add --move-to-nearest-code / target.move-to-nearest-code options

[jingham at apple.com]

You would have to do the exact match check slightly differently in the resolver.  Instead of just calling into ResolveSymbolContext with one or the other value of exact match, call with exact_match = false.  If you got a result, but the line number didn't match, make a new location anyway but set the not yet existing "not-enabled-because-of-exact-match" flag.  Then you'll have to make IsEnabled on the locations check both the enabled flag and the "not-enabled-because-of-exact-match" flags.

Jim


> On May 14, 2015, at 10:31 AM, Ilia K <ki.stfu at gmail.com> wrote:
> 
> In http://reviews.llvm.org/D9273#172247, @jingham wrote:
> 
>>  3.1: where = a.out`main + 20 at main.c:12, not resolved because exact_match = 1, moved address = 0x0000000100000eb4
> 
> 
> How I can determine why it wasn't resolved? (I mean, it wasn't resolved due to exact_match=1, or symbols just not loaded yet?)
> 
> 
> http://reviews.llvm.org/D9273
> 
> EMAIL PREFERENCES
>  http://reviews.llvm.org/settings/panel/emailpreferences/
> 
>