Greg, Mark,
Looking at the code, LLDB falls back to a full file crc32 to create the
module UUID if the ELF build-id is missing. This works, in the sense that
the generated UUID does indeed identify the module.
But there are a few problems with this approach:
1. First, runtime performance: a full
Am Fr., 3. Aug. 2018 um 16:42 Uhr schrieb Leonard Mosescu :
>
> +1, really nice. Any plans to add wall clock time? (I see you're using perf,
> right?)
It's on my own VPS where I also run other things, so instruction count
is used for the long-term graph to prevent that other processes make
the gr
+1, really nice. Any plans to add wall clock time? (I see you're using
perf, right?)
On Fri, Aug 3, 2018 at 3:59 PM, Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> This is really cool. Maybe you could do it for all of LLVM too? It would
> be nice if, instead of cycling through
This is really cool. Maybe you could do it for all of LLVM too? It would
be nice if, instead of cycling through each benchmark on a set interval,
there were just a dropdown box where you could select the one you wanted to
see.
On Fri, Aug 3, 2018 at 3:37 PM Raphael Isemann via lldb-dev <
lldb-de
Paul,
Are you using llvm-project-20170507.git ?
Regarding to release_70, I am updating it manually, due to each
repo.git/release_70 might not be up-to-date. In fact, openmp.git/release_70
isn't yet.
Sorry for the inconvenience. Please be patient.
On Fri, Aug 3, 2018 at 10:44 PM via llvm-dev
wr
Hi everyone,
I wanted to share a (hopefully useful) service for LLDB that I added recently:
If you go to https://teemperor.de/lldb-bench/ you'll now see graphs
that show the instruction count and memory usage of the last LLDB
nightlies (one per day). If you click on a graph you'll see a flame
gra
https://bugs.llvm.org/show_bug.cgi?id=38443
Bug ID: 38443
Summary: "log enable dwarf all" introduces deadlocks
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Thanks! I look forward to the patch.
Jim
> On Aug 2, 2018, at 8:56 PM, Venkata Ramanaiah Nalamothu
> wrote:
>
> Thanks Jim for the elaborate reply.
>
> I knew what is happening in below piece of code and also has a patch ready
> but now needs a bit of fine tuning based on your below commen
> -Original Message-
> From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf Of Hans
> Wennborg
> Sent: Friday, August 03, 2018 9:40 AM
> To: Robinson, Paul
> Cc: Release-testers; llvm-dev; openmp-dev (openmp-...@lists.llvm.org);
> LLDB Dev
> Subject: Re: [cfe-dev] [7.0.0 Rel
On Fri, Aug 3, 2018 at 3:38 PM, wrote:
> Hi Hans,
>
> I was just trying to push a release note about DWARF v5 support. I did:
> git checkout release_70 # in the monorepo
> git commit
> git llvm push
> but that fails. How do you want to do release notes?
I'm not familiar with "git llvm",
Hi Hans,
I was just trying to push a release note about DWARF v5 support. I did:
git checkout release_70 # in the monorepo
git commit
git llvm push
but that fails. How do you want to do release notes?
Thanks,
--paulr
> -Original Message-
> From: cfe-dev [mailto:cfe-dev-boun...@li
Dear testers,
7.0.0-rc1 was just tagged (from the branch at r338847).
It's early in the release process, but I'd like to find out what the
status is of the branch on our various platforms.
Please run the test script, share the results, and upload binaries.
Thanks,
Hans
_
Hi Gábor,
That error is kind of correct. As far as c++ standard is concerned,
this is an ODR violation, as both lldb and liblldb link in a copy of
LLVMSupport.a. However, all LLVM symbols in liblldb have "hidden"
visibility (and we make sure we don't pass around llvm objects on the
SO boundary), s
Hi Vedant and Pavel,
Thanks for your reply.
I agree that asan may report false positives in case of leak
detection: E.g. library A (instrumented) allocates memory, while
library B (not instrumented by asan) is responsible for deallocation.
However, my goal is to discover memory corruption errors a
When I looked into this in the past (two years ago), the problem was
that the sanitizer runtimes were expected to be linked into the main
executable. For the dotest tests, the main executable is "python", so
unless you have built an asanified python, you will not have them.
You might be able to ge
15 matches
Mail list logo
