On 11 August 2015 at 17:17, Mike McLaughlin wrote:
> Any word on the fix for Linux? I really don't know enough to fix it myself.
> Would this fix (and any Linux, etc. fix) go into 3.7?
I think it's going to be too late for 3.7 since we don't have the fix
in place yet. I'm not aware of the Linu
There's also test\expression_command\issue_11588, which is especially
confusing because the comments and symbols in the test are actually
numbered 11581.
On Fri, Aug 14, 2015 at 11:58 AM, Enrico Granata via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
> On Aug 14, 2015, at 11:50 AM, Zachary Turne
> On Aug 14, 2015, at 11:50 AM, Zachary Turner via lldb-dev
> wrote:
>
> There are a bunch of tests in the tree that are named after Rdars. As a
> result, it's not clear to anyone outside of Apple what these are supposed to
> be testing so it diminishes their usefulness and increases our mai
There are a bunch of tests in the tree that are named after Rdars. As a
result, it's not clear to anyone outside of Apple what these are supposed
to be testing so it diminishes their usefulness and increases our
maintenance burden since it's impossible to know if it is an issue that we
should fix,
> On Aug 14, 2015, at 11:04 AM, Bruce Mitchener
> wrote:
>
> I was doing some more digging into this and experimentation and found that
> the Windows build appears to handle this already, but that's because symbol
> visibility is different over there.
>
> It looks like on non-Windows, we sho
https://llvm.org/bugs/show_bug.cgi?id=21721
Zachary Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=21727
Bug 21727 depends on bug 21721, which changed state.
Bug 21721 Summary: Fix the test runner to correctly set PATH for shared libs on
Windows
https://llvm.org/bugs/show_bug.cgi?id=21721
What|Removed |Added
---
Hmm, while the below would help, it wouldn't prevent the llvm and clang
symbols from being re-exported from the LLDB shared library.
I still think it would be good to do, but we'd still need the linker
options (but that's easy for Darwin, a bit more involved for Linux and
FreeBSD, I think).
- Br
I was doing some more digging into this and experimentation and found that
the Windows build appears to handle this already, but that's because symbol
visibility is different over there.
It looks like on non-Windows, we should be using the
__attribute__((visibility("hidden"))) for pretty much all
https://llvm.org/bugs/show_bug.cgi?id=24462
Bug ID: 24462
Summary: Fix data formatters on Windows
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Prior
https://llvm.org/bugs/show_bug.cgi?id=24461
Bug ID: 24461
Summary: Allow LLDB to support Python 3.5
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Pri
https://llvm.org/bugs/show_bug.cgi?id=21920
Zachary Turner changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=22210
Zachary Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=21930
Zachary Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=21720
Zachary Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=21767
Zachary Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=21730
Zachary Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=24460
Bug ID: 24460
Summary: Make STL data formatters for Windows
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
> On Aug 14, 2015, at 12:25 AM, Abhishek Aggarwal
> wrote:
>
> Hi
>
> As per my understanding (please correct if I am wrong):
>
> 1. There exists a file for each platform (Architecture+OS) that calculates
> the offsets for that platform. e.g. RegisterContextLinux_x86_64.cpp for
> x86_64 arc
> On Aug 13, 2015, at 6:43 PM, Bruce Mitchener via lldb-dev
> wrote:
>
> 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.
It currently exports:
_ZN4lldb
https://llvm.org/bugs/show_bug.cgi?id=23718
abhiinnit...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=24457
abhiinnit...@gmail.com changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |abhiinnit...@gmail.com
--
You are rece
https://llvm.org/bugs/show_bug.cgi?id=24457
Bug ID: 24457
Summary: register read --all provides wrong values of FPU flags
for x86_64 Linux p;atform
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Hi
As per my understanding (please correct if I am wrong):
1. There exists a file for each platform (Architecture+OS) that calculates
the offsets for that platform. e.g. RegisterContextLinux_x86_64.cpp for
x86_64 architecture on Linux OS.
2. For each platform, offset values for registers might b
24 matches
Mail list logo
