In theory what you're doing looks like it should be supported. I am not sure
why your example is failing the way it is.
Is your variable a global maybe?
Also, using the variable name is the wrong thing to do. If you have a class
with a std::string member, the name is going to return the wrong t
> On Apr 13, 2016, at 10:11 AM, Jeffrey Tan wrote:
>
> One quick question: do we support getting type summary string from inferior
> method call?
No - for that you are going to need to write a Python formatter.
Running code in formatters is a risky endeavor for a bunch of reasons, so it is
b
I did a quick testing to call SBFrame.EvaluateExpression('string.c_str()')
for the summary. The result shows valobj.GetFrame() returns None so does
this mean this is not supported?
def DoTest(valobj,internal_dict):
print "valobj: %s" % valobj
print "valobj.GetFrame(): %s" % valobj.GetFrame
One quick question: do we support getting type summary string from inferior
method call? After reading our own fbstring_core code, I found I need to
mirror a lot of what fbstring_core.c_str() method is doing in python. I
wonder if we can just call ${var.c_str()} as the type summary? I suspect
one o
https://llvm.org/bugs/show_bug.cgi?id=27336
Bug ID: 27336
Summary: Float128 not handled in ClangASTContext::GetEncoding
Product: lldb
Version: unspecified
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: nor
Well the point of the user ids was to support multiple trace technologies
for the same thread, so in that case the thread id is not sufficient for
uniquely identifying the trace. Now I guess the server would need to be
aware of the user-id if multiple trace technologies are active on the same
threa
Do we need the server to know about the user ids we handed out to the
SB API client? AFAIK, you cannot have multiple traces of the same
thread running concurrently, so a thread-id should uniquely identify a
trace. The user id can then stay a client thing for abstracting the
concrete implementation
Hello,
Ok for the thread id we may use this QThreadSuffixSupported
extension but gdb packets also *don't have userid support *since gdb does
not have the concept of user id for trace instances. Also gdb uses seperate
packets for trace configuration and starting the trace.
On Tue, Apr 12, 20
