Hello,
On Mac OS X, when using the xcode projects, there is some machinery to
manage what symbols are exported from various things:
- liblldb only exports the public API.
- debugserver only exports _DNB* and __DNB*
- argdumper exports nothing
- lldb-server exports nothing
This machi
https://llvm.org/bugs/show_bug.cgi?id=24452
Bug ID: 24452
Summary: Get lldb-mi tests working on Windows
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=24450
Bug ID: 24450
Summary: Assertion failed: (width > BitWidth && "Invalid APInt
SignExtend request")
Product: lldb
Version: unspecified
Hardware: PC
OS: All
https://llvm.org/bugs/show_bug.cgi?id=24446
Bug ID: 24446
Summary: Support watchpoints on Windows
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Prior
There are also a few competing log implementations. There are ones like in
"source/Core/Logging.cpp" which are hard coded, and then there is a plugin
version as you can see in LogChannelDWARF.cpp. The latter is the newer way to
implement custom log channels without hand coding a copy of
"source
All registers are placed into one large buffer that contains everything. All
offsets should be the global offset in the register context's data. Typically
we should see:
GPR
rax offset 0
rbx offset 8
FPR
mm0 offset 128
mm1 offset 160
...
EXC
fpsr offset 256
...
So
Thank you for the link to the previous discussion and the description of
the Windows logging. I like the idea of the macro based logging on Windows
but agree that the explicit log channel definition is a bit too verbose.
Currently I would prefer a mixed solution with 'Log* log = ...; LOG_IF(log,
"
Hello
I have a question regarding offset calculations of registers for x86_64
architecture. In file source/Plugins/Process/Utility/RegisterInfos_x86_64.h:
The macro FPR_OFFSET(reg) calculates the offset of floating point
register 'reg' with respect to 'UserArea' struct while GPR_OFFSET(reg)
calcu
