t;: jc 0xb
>>>> (lldb) break list
>>>> Current breakpoints:
>>>> 1: name = 'main', locations = 1
>>>> 1.1: where = tile.elf`main + 16 at token_pass.c:74, address =
>>>> tile.elf[0x0410], unresolved, hit count = 0
>>>>
ember 8, 2018 1:39 PM
To: Adrian Harris
Cc: ted.woodw...@codeaurora.org; LLDB
Subject: Re: [lldb-dev] problem resolving symbolic breakpoint on a remote
target
> On Nov 8, 2018, at 11:18 AM, Adrian Harris wrote:
>
> Thanks Jim - that makes sense for the types of targets that lldb
gt;> So it is still not resolved.
>>>
>>> Adrian
>>>
>>>
>>>> On Nov 8, 2018, at 11:06 AM, ted.woodw...@codeaurora.org wrote:
>>>>
>>>> What happens if you do this:
>>>>
>>>> (lldb) file tile.elf
>>
>>
>>> On Nov 8, 2018, at 11:06 AM, ted.woodw...@codeaurora.org wrote:
>>>
>>> What happens if you do this:
>>>
>>> (lldb) file tile.elf
>>> (lldb) b main
>>> (lldb) gdb-remote
>>>
>>> ?
>>>
;>
>> What happens if you do this:
>>
>> (lldb) file tile.elf
>> (lldb) b main
>> (lldb) gdb-remote
>>
>> ?
>>
>> --
>> Ted Woodward
>> Qualcomm Innovation Center, Inc.
>> Qualcomm Innovation Center, Inc. is a member of
s
> via lldb-dev
> Sent: Thursday, November 8, 2018 11:09 AM
> To: via lldb-dev
> Subject: [lldb-dev] problem resolving symbolic breakpoint on a remote target
>
> Hi Everyone,
>
> I'm unable to resolve *symbolic* breakpoints on a gdb-remote target. Address
> breakp
Behalf Of Adrian Harris via
lldb-dev
Sent: Thursday, November 8, 2018 11:09 AM
To: via lldb-dev
Subject: [lldb-dev] problem resolving symbolic breakpoint on a remote target
Hi Everyone,
I'm unable to resolve *symbolic* breakpoints on a gdb-remote target. Address
breakpoints work fine. I suspect
Hi Everyone,
I'm unable to resolve *symbolic* breakpoints on a gdb-remote target. Address
breakpoints work fine. I suspect this is probably some form of user-error, but
I've had no luck figuring it out on my own.
My target has llvm support and lldb has been patched to add a new target as
well.
