On 26 June 2017 at 18:19, Chris Quenelle via lldb-dev
wrote:
>
> My main concern was that *if* strings are added, there's some
> clear documentation about the relationship between the string
> and the number to explain what's going on. Based on other
> emails in this thread it seems like the numb
https://bugs.llvm.org/show_bug.cgi?id=33603
lab...@google.com changed:
What|Removed |Added
CC||lab...@google.com
Assignee|lldb-de
Hello,
I would just like to add one more point to this discussion about
error strings being human readable or not, I guess the whole purpose
of having error strings, is to present them to human users right ? i mean a
use case of sending strings, that are not human readable won't be
required.
Hello,
I am running lldb-3.8 on rpi2.
When I load coredump file, lldb exited with seg fault.
After digging into this issue, I found that loading core file for 32bit arch
does not work well.
Last commit for 32bit arch corefile is
" From 109a39c9709dbc2bd689469f1ba15efee098ee41 Mon Sep 17 00:00:0
Hi,
Could someone please help me on the below?
Thanks,
Ramana
On Mon, Jun 12, 2017 at 11:58 AM, Ramana wrote:
> Hi,
>
> I have to implement a debugger for our HW which comprises of CPU+GPU where
> the GPU is coded in OpenCL and is accelerated through OpenVX API in C++
> application which runs
