Thank you very much for tracking this down.
+1 for making UniqueCStringMap speak ConstString -- i think it just makes
sense given that it already has "unique" in the name.
ConstString already has a GetStringRef accessor. Also adding a conversion
operator may be a good idea, although it probably w
On 19 April 2017 at 19:15, Scott Smith wrote:
> A combination of:
> 1. Updating to a known good release according to buildbot
> 2. using Ubuntu 14.04
> 3. compiling release using clang-4.0
>
I'd hope that the compiler used to build lldb does not matter. If you see
any differences due to this fact
AFAIK the Ubuntu 14.04 cmake builder runs tests using ToT clang (built on
the build bot) as step test3 and test4 and it seems to be green so if you
are seeing different result then I would expect it to be caused by a
configuration difference between the setup the bot has and you have (or the
bot ru
On 20 April 2017 at 15:01, Tamas Berghammer wrote:
> AFAIK the Ubuntu 14.04 cmake builder runs tests using ToT clang (built on
> the build bot) as step test3 and test4 and it seems to be green so if you
> are seeing different result then I would expect it to be caused by a
> configuration differe
Hi,
this is a known problem and somewhat embarrassing problem, but
unfortunately we haven't had time to look at that yet. The code that is
doing that was added to support loading of the vdso, which is only present
in the application memory (and it is a full elf file). I don't think
anybody has rea
Hi, been seeing an issue very frequently while single-stepping a remote
multithreaded iOS target. Host is OS X. The crash is in
ProcessGDBRemote::WillPublicStop, close to NULL. I downloaded the latest
source from git and compiled a debug version. Same scenario crashed in
assertion in GetItem
Hey Pavel,
What would be a reasonable solution?
Does having the lldb-server read the shared libraries from disk (instead of
from the process's memory) sound sensible?
Scott
On Thu, Apr 20, 2017 at 10:30 AM, Pavel Labath wrote:
> Hi,
>
> this is a known problem and somewhat embarrassing proble
What's the preferred way to post changes? In the past I tried emailing
here but it was pointed out I should send to lldb-commit instead. But,
there's also phabricator for web-based code reviews.
So,
1. just email lldb-commits?
2. post on http://reviews.llvm.org/?
On Thu, Apr 20, 2017 at 3:16 A
#2 is preferred. When you do it, make sure to add lldb-commits in the
subscribers field. You're also free to add specific people to the
reviewers field, but the mailing list specifically has to be on
subscribers. Unfortunately, due to what I assume are bugs in Phabricator,
if you don't get the s
Thanks, Ed Maste is the current FreeBSD maintainer.
On 20.04.2017 07:36, vignesh balu wrote:
> Created Review : https://reviews.llvm.org/D32271
>
> Do i need to assign the reviewers ? if so please let me know how to get
> reviewers list.
>
> -vbalu
>
>
> On Wed, Apr 19, 2017 at 7:59 PM, Kamil
On Thu, Apr 20, 2017 at 6:47 AM, Pavel Labath wrote:
> 5. specifying gcc-4.8 instead of the locally compiled clang
>
> has most of the tests passing, with a handful of unexpected successes:
>>
>> UNEXPECTED SUCCESS: TestRegisterVariables.Register
>> VariableTestCase.test_and_run_command_dwarf
>>
Sorry, I take that back. I forgot to save the buffer that ran the test
script. Oops :-(
I get a number of errors that make me think it's missing libc++, which
makes sense because I never installed it. However, I thought clang
automatically falls back to using gcc's libstdc++.
Failures include:
On 20 April 2017 at 19:42, Scott Smith wrote:
> Sorry, I take that back. I forgot to save the buffer that ran the test
> script. Oops :-(
>
> I get a number of errors that make me think it's missing libc++, which
> makes sense because I never installed it. However, I thought clang
> automatica
13 matches
Mail list logo
