https://bugs.llvm.org/show_bug.cgi?id=37190
ema...@freebsd.org changed:
What|Removed |Added
OS|Windows NT |FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=37190
Bug ID: 37190
Summary: 'memory read' reports 0s for unreadable memory on
FreeBSD
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
> On Apr 20, 2018, at 12:17 PM, Pavel Labath wrote:
>
> On Fri, 20 Apr 2018 at 17:14, Greg Clayton wrote:
>>> On Apr 20, 2018, at 1:08 AM, Pavel Labath wrote:
>>>
>>>
>>> So, I can see the case for both, and I don't really have a
If I run the llvm lit tests with the debug build of Python, I get the same
kind of errors, so I think this is a bug in lit that we haven't seen
because people have been using it with non-debug Python. I'm investigating
that angle.
On Fri, Apr 20, 2018 at 12:21 PM, Ted Woodward via lldb-dev <
See my comment in https://reviews.llvm.org/D45333 .
r330275 changed how lldb’s lit tests were set up. This gives cmake errors using
the Visual Studio generator; I wouldn’t be surprised if what you’re seeing
using ninja is the same issue.
Short version: the cmake code that sets up the lit
On Fri, 20 Apr 2018 at 17:14, Greg Clayton wrote:
> > On Apr 20, 2018, at 1:08 AM, Pavel Labath wrote:
> >
> >
> > So, I can see the case for both, and I don't really have a clear
> > preference. All I would say is, whichever way we choose, we should make
I'm trying to figure out what's happening with the LLDB lit tests on
Windows. I'm not sure how to proceed with debugging this.
I execute this command:
ninja check-lldb
And several things happen very rapidly:
1. On the console, I get one warning that says:
>> Yes, that's exactly what the author of this test (me) had in mind. :)>> And it's not just a hypothetical posix thing either. Windows and cygwin>> both use \\ and // to mean funny things. I remember also seeing something>> like that on linux, though I can't remember now what was it being used
> On Apr 20, 2018, at 1:08 AM, Pavel Labath wrote:
>
> On Thu, 19 Apr 2018 at 19:20, Zachary Turner via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>
>
>> On Thu, Apr 19, 2018 at 11:14 AM Greg Clayton via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>
>>> Also,
r329889 says "Use in-tree dsymutil on Darwin", but it's got these change in
test/CMakeLists.txt:
-set(LLDB_TEST_DEPS lldb)
+set(LLDB_TEST_DEPS lldb dsymutil)
...
+ --dsymutil $
These changes aren't gated by a check for Darwin, so they happen on all
systems. On my machine (Ubuntu 14), which
Maybe Kalimba developers can help here. Kalimba has crazy memory map...:-)
--
Zdenek
On 04/19/2018 08:32 PM, Ted Woodward wrote:
Hexagon has a single address space, so we don't need to do anything like this.
When I worked on Motorola 56xxx DSPs we had memory spaces, but we didn't use
RSP. We
On 04/19/2018 08:22 PM, Jim Ingham wrote:
On Apr 19, 2018, at 10:54 AM, Greg Clayton wrote:
On Apr 19, 2018, at 10:35 AM, Jim Ingham wrote:
On Apr 19, 2018, at 9:44 AM, Greg Clayton via lldb-dev
wrote:
On Apr 19,
On Thu, 19 Apr 2018 at 19:20, Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> On Thu, Apr 19, 2018 at 11:14 AM Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>> Also, looking at the tests for normalizing paths I found the following
pairs of pre-normalized and
13 matches
Mail list logo