This can also be reproduced in the command line like this:
(lldb) expr "foo"
(const char [4]) $0 = "foo"
(lldb) expr "bar"
(const char [4]) $1 = "bar"
(lldb) expr $0
(const char [4]) $0 = “bar”
This however works just fine:
(lldb) expr char c[] = "foo"; c
(char [4]) $0 = "foo"
(lldb) expr char c
https://bugs.llvm.org/show_bug.cgi?id=44155
Raphael Isemann changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |teempe...@gmail.com
Status|NEW
https://bugs.llvm.org/show_bug.cgi?id=44155
Bug ID: 44155
Summary: LLDB doesn't preserve values of strings
Product: lldb
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Hi,
I am trying to figure out the proper way of using LLDB's SBLaunchInfo class:
When I launch a process via CLI interpreter, it seems to receive all of the
environment variables inherited from shell, plus the ones I set via
`target.env-vars`:
(lldb) file /usr/bin/env
Current executable set to '/u
https://bugs.llvm.org/show_bug.cgi?id=44151
Bug ID: 44151
Summary: llvm-pdbutil: An unknown error has occurred. HRESULT:
0x8007007E: Calling NoRegCoCreate
Product: lldb
Version: unspecified
Hardware: PC
OS:
Hi,
We're running into a problem where a Python SBValue references stale
memory. It can be reproduced by evaluating an expression with a constant
string:
var1 = frame.EvaluateExpression("\"ABCDEFGEH\"")
var2 = frame.EvaluateExpression("\"123456789\"")
print(var1.GetSummary())
prin
https://bugs.llvm.org/show_bug.cgi?id=44056
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Windows is ready:
$ sha256sum LLVM-9.0.1-rc1*.exe
bf04775d245bbf3ac9dc79f14b6e2ccffcda06ab8edd999cabd28bd8dfa894a9
LLVM-9.0.1-rc1-win32.exe
78f5cab932b6194f9fc3f0d6dc9b30d3c1449ddd848bdc9ca61cb2fde67072d7
LLVM-9.0.1-rc1-win64.exe
It was built using the attached batch file.
Thanks,
Hans
On Sat,
