On Wed, 8 Jan 2020, Jonas Devlieghere wrote:
Yes, that's correct. This was added in edadb818e5b.
Thanks!
// Martin
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
On 01/08/2020 09:24 AM, Brian Cain wrote:
> Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release
> page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1
>
The binaries have been posted now.
> I also checked https://releases.llvm.org/ because I recall some de
Thanks for clarification.
>> It would make sense to pass the summary provider the requested format.
>> SBValue has a GetFormat option, so if the format was properly set on the
>> SBValue before it's passed to the summary provider, that would work already.
>> Then it's up to the summary provid
On Wed, Jan 8, 2020 at 2:46 PM Adrian Prantl wrote:
>
>
>
> > On Jan 6, 2020, at 11:17 AM, Jonas Devlieghere via lldb-dev
> > wrote:
> >
> > Hey everyone,
> >
> > I just wanted to let you know that most of the work is complete for
> > auto-detecting optional dependencies in LLDB. Unless explicit
> On Jan 6, 2020, at 11:17 AM, Jonas Devlieghere via lldb-dev
> wrote:
>
> Hey everyone,
>
> I just wanted to let you know that most of the work is complete for
> auto-detecting optional dependencies in LLDB. Unless explicitly
> specified, optional dependencies like editline will be enabled w
Yes, that's correct. This was added in edadb818e5b.
On Tue, Jan 7, 2020 at 11:19 PM Martin Storsjö wrote:
>
> On Tue, 7 Jan 2020, Jonas Devlieghere wrote:
>
> > After trying it out I concluded that it should be easy enough to check
> > for the static bindings flag in FindPythonInterpAndLibs.cmake
Hi,
I was recently working on a debugging utility code in my app that ultimately
needed to access some of the non-exported symbols from a linked shared library.
This code would only be run under DEBUG builds and is only useful when
debugger's CLI is present. With that constraint I hoped to some
The way lldb works, char[] has a type summary that does two things, 1) presents
the contents as a C-string, and 2) suppresses the actual printing of the
elements. If it hadn't done (2) then you would have seen the elements
formatted as a vector of char's with the format you specified. OTOH (2)
Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release
page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1
I also checked https://releases.llvm.org/ because I recall some debate or
back-and-forth about where the releases should go and/or redirects or links
from
Hi everyone,
This is just a quick reminder that the upcoming release branch is
scheduled for one week from today: Wednesday, 15 January 2020.
When the branch is created, the trunk version will become 11.0.0.
The full release schedule can be found under "Upcoming Releases" in
the column to the ri
Hello,
I am trying to debug a simple c program,
int main() {
char arr[] = "Hello World!";
}
On gdb, while printing variable content with force formatting,
(gdb) l
1 int main() {
2 char arr[] = "Hello World!";
3 }
(gdb) b 3
Breakpoint 2 at 0x40050a: file string.c, lin
11 matches
Mail list logo
