Btw: after patching with Siva's fix http://reviews.llvm.org/D18008, the
first field 'small_' is fixed, however the second field 'ml_' still emits
garbage:
(lldb) fr v corpus
(const string &const) corpus = error: summary string parsing error: {
store_ = {
= {
small_ = "www"
ml_ =
Thanks David. I meant to send to lldb maillist, but glad to hear response
here.
Our binary is built from gcc:
String dump of section '.comment':
[ 1] GCC: (GNU) 4.9.x-google 20150123 (prerelease)
Is there any similar flags we should use? By doing "strings -a [binary] |
grep -i gcc", I foun
Sorry, sent to the wrong alias.
-- Forwarded message --
From: Jeffrey Tan
Date: Sat, Mar 26, 2016 at 3:19 PM
Subject: DW_TAG_member extends beyond the bounds error on Linux
To: llvm-...@lists.llvm.org
Hi,
While dogfooding our lldb based IDE on Linux, I am seeing a lot of variab
Follow-up for the previous question:
Our python code is trying to call json.dumps to serialize the variable
evaluation result into string block and send to IDE via RPC, however it
failed with "UnicodeDecodeError: 'utf8' codec can't decode byte 0xc9 in
position 10: invalid continuation byte" becaus
