Hi Jason
Thanks for the advice - I've been surprised overall how capable DWARF
expressions are so wouldn't have been surprised to learn that there is
also a category of pseudo-variables (not that I can think of any
others, or other circumstances where it would be useful: the usual
combined code/da
Many thanks!
I've added all binaries I've got so far to the pre-release page now
(the CDN might take a while to invalidate its cache).
On Tue, Mar 5, 2019 at 1:56 AM Brian Cain wrote:
>
> Uploaded SLES11, Ubuntu 14.04, 18.04 binaries.
>
> 9e59c0c667cd67c61600470d2e3107576b4707c8
> clang+llvm-8
Hi,
On trunk I receive the following build error on Linux:
../../git/llvm/tools/lldb/include/lldb/lldb-forward.h:181:7: note:
forward declaration of 'lldb_private::ProcessInstanceInfoList'
class ProcessInstanceInfoList;
^
../../git/llvm/tools/lldb/source/Host/linux/Host.cpp:260:23: error:
me
Hans,
Where can I find a win64 bit libclang.dll to test.
Iv just updated from 6.0 to 7.0 and tried 7.01 and found that libclang 7+
doesn't recognise my include arguments.
Downgrading to 6.0 fixes the issue for me.
Kind Regards
Dan
From: cfe-dev on behalf o
On 04/03/2019 11:46, Thomas Goodfellow via lldb-dev wrote:
I'm adding LLDB support for an unconventional platform which uses two
stacks: one purely for return addresses and another for frame context
(spilled registers, local variables, etc). There is no explicit link
between the two stacks, i.e.
On Sun, 03 Mar 2019 04:17:42 +0100, Mason Kramer via lldb-dev wrote:
> Then, I restricted the acceptable range of
> gdbserver ports to just 5001, using the flags suggested in the email.
>
> lldb-server-4.0 platform --verbose --listen "*:5000" --min-gdbserver-port
> 5001 --max-gdbserver-port 5001
I think this might have been fixed, try to pull.
On Tue, Mar 5, 2019 at 3:10 AM Gábor Márton via lldb-dev
wrote:
>
> Hi,
>
> On trunk I receive the following build error on Linux:
> ../../git/llvm/tools/lldb/include/lldb/lldb-forward.h:181:7: note:
> forward declaration of 'lldb_private::ProcessI
Hello all,
I have just posted a large-ish patch series for review (D58971, D58973,
D58975, D58976), and I want to use this opportunity to draw more
attention to it and highlight various bikeshedding
opportunities^H^H^Htopics for discussion :).
The new tool is called core2yaml, and it's goal
Yes, it works. Thanks!
On Tue, Mar 5, 2019 at 4:54 PM Davide Italiano wrote:
>
> I think this might have been fixed, try to pull.
>
> On Tue, Mar 5, 2019 at 3:10 AM Gábor Márton via lldb-dev
> wrote:
> >
> > Hi,
> >
> > On trunk I receive the following build error on Linux:
> > ../../git/llvm/to
Yeah, if you don't need to find a way to express this in DWARF, then adding a
type to RestoreType would be very simple. lldb maps all the different unwind
sources (debug_frame, eh_frame, arm index, compact unwind, assembly instruction
scanning) into its internal intermediate representation (Unw
Hi Pavel,
On Tue, Mar 5, 2019 at 8:31 AM Pavel Labath via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hello all,
>
> I have just posted a large-ish patch series for review (D58971, D58973,
> D58975, D58976), and I want to use this opportunity to draw more
> attention to it and highlight various
On Tue, Mar 5, 2019 at 1:47 PM Jonas Devlieghere via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
> I don't know much about the minidump format or code, but it sounds
> reasonable for me to have support for it in yaml2obj, which would be a
> sufficient motivation to have the code live there. As yo
12 matches
Mail list logo
