[lldb-dev] [CFP] LLVM devroom @ FOSDEM 2017
CALL FOR PAPERS / PARTICIPATION At FOSDEM 2017, LLVM will again participate with a dedicated devroom. Complementing the upcoming Euro LLVM 2017, the devroom at FOSDEM provides a great opportunity for LLVM developers and the wider open source community to get together, connect and discuss. As possibly the largest European Open Source Conference, FOSDEM takes place in Brussels and attracts with more than 400 lectures every year over 5000 hackers - many core contributors of the worlds leading open source projects. = Call for Speakers, Posters, Demos = We invite academic, industrial and hobbyist speakers to present their work on developing or using LLVM, Clang, LLDB, Polly, Compiler-RT, etc. We are looking for: 1. Keynote speakers. 2. Technical presentations (30 minutes plus questions and discussion) related to development of LLVM, Clang etc. 3. Presentations about the use of LLVM, Clang in commercial, academic, hobbyist and other projects. 4. Tutorials. 5. Lightning talks (5 minutes). The deadline for receiving submissions is December 1st, 2016. Speakers will be notified of acceptance or rejection by the 15th of December. Proposals that are not sufficiently detailed (talks lacking a comprehensive abstract for example) are likely to be rejected. Please create an account on the FOSDEM interface ( https://penta.fosdem.org/user/new_account ) and submit your proposal ( https://penta.fosdem.org/submission/FOSDEM17 ). Please make sure you select "LLVM devroom" as the "Track". = Registration = FOSDEM does not require any registration and is free of charge. However, just like last year, a large crowd must be expected. We have had to refuse entry to the room every year due to health and safety reasons (a hard requirement from the organisers), with the room already packed with people standing. = Organization = The mailing list llvm-devroom at lists.fosdem.org can be used to discuss issues of general interest related to the conference organization. Please, do not reply to this email, as it is cross posted to many lists. = Financial Support = There may be a possibility of limited funding to help students or contributors who could not otherwise attend the conference. This will depend on overall sponsorship and companies' interest in supporting the event. If you need funding to attend the meeting, or can help sponsor, please tell us on llvm-devroom at lists.fosdem.org. = About LLVM = LLVM is a collection of libraries and tools that make it easy to build compilers, optimizers, Just-In-Time code generators, and many other compiler-related programs. LLVM uses a single, language-independent virtual instruction set both as an offline code representation (to communicate code between compiler phases and to run-time systems) and as the compiler internal representation (to analyse and transform programs). This persistent code representation allows a common set of sophisticated compiler techniques to be applied at compile-time, link-time, install-time, run-time, or "idle-time" (between program runs). The strengths of the LLVM infrastructure are its extremely simple design (which makes it easy to understand and use), source-language independence, powerful mid-level optimizer, automated compiler debugging support, extensibility, and its stability and reliability. LLVM is currently being used to host a wide variety of academic research projects and commercial projects. Besides LLVM, several projects have been developed on top of it like Clang, LLDB, LLD or Polly. For more information, please visit http://llvm.org/ or the conference webpage at http://llvm.org/devmtg/2017-02/ Best regards, LLVM @ FOSDEM organisers ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB can't find source...but it can?
> On Oct 7, 2016, at 4:53 PM, Ted Woodward via lldb-dev
> wrote:
>
> Background – I’m working on getting LLDB to run on Hexagon Linux, built with
> an LLVM toolchain. We’re using libc++ and MUSL. The loader is a bit
> squirrelly right now, so I’ve built LLDB statically.
>
> I’ve got full source debugging in the driver, but when I step into
> SBDebugger::Create, I don’t have any source. I’ve got symbols:
> (lldb) bt
> * thread #1: tid = 1, 0x00114730 lldb`lldb::SBDebugger::Create(bool) + 16,
> stop reason = breakpoint 2.1
> * frame #0: 0x00114730 lldb`lldb::SBDebugger::Create(bool) + 16
> frame #1: 0x01dc lldb`Driver::Driver(this=0x7ffefc50) + 124 at
> Driver.cpp:150
> frame #2: 0x6aa0 lldb`main(argc=1, argv=0x7ffefd34) + 240 at
> Driver.cpp:1350
> frame #3: 0x04744384 lldb`__libc_start_main + 48
>
> list SBDebugger::Create fails, but list SBDebugger::Create(bool) gives me
> source.
> (lldb) list SBDebugger::Create
> (lldb) list SBDebugger::Create(bool)
> File: \local\mnt\workspace\ted\linux\llvm\tools\lldb\source\API\SBDebugger.cpp
>172 return SBDebugger::Create(false, nullptr, nullptr);
>173 }
>174
>175 SBDebugger
>176 SBDebugger::Create(bool source_init_files)
>177 {
>178 return SBDebugger::Create (source_init_files, nullptr, nullptr);
>179 }
>180
>181 SBDebugger
>182 SBDebugger::Create(bool source_init_files, lldb::LogOutputCallback
> callback, void *baton)
>183
>
> Finally, I try to list based on the address of the function:
> (lldb) list 0x114720
> error: address resolves to lldb[0x00114720], but there is no line
> table information available for this address.
>
> But there is line table information for 0x114720 (from llvm-dwarfdump):
> 0x00114720177 0 80 0 0 is_stmt
> 0x00114730178 32 80 0 0 is_stmt
> prologue_end
> 0x00114734178 12 80 0 0
> 0x00114754178 5 80 0 0
>
>
>
> My breakpoint at SBDebugger::Create resolved to prologue_end:
> (lldb) break list
> Current breakpoints:
> 1: name = 'main', locations = 1, resolved = 1, hit count = 1
> 1.1: where = lldb`main + 32 at Driver.cpp:1335, address = 0x69d0,
> resolved, hit count = 1
>
> 2: name = 'SBDebugger::Create', locations = 3, resolved = 3, hit count = 1
> 2.1: where = lldb`lldb::SBDebugger::Create(bool) + 16, address =
> 0x00114730, resolved, hit count = 1
> 2.2: where = lldb`lldb::SBDebugger::Create() + 8, address = 0x001143c0,
> resolved, hit count = 0
> 2.3: where = lldb`lldb::SBDebugger::Create(bool, void (*)(char const*,
> void*), void*) + 40, address = 0x00114404, resolved, hit count = 0
>
>
> So – why can LLDB find the source when I specify the function explicitly, or
> find the line table info when I set a breakpoint, but not when I am in the
> function or list an address?
>
Probably a debug info problem. Before we know to look for addresses within a
compile unit, the compile unit must claim it has a function that contains this
address. So check the DWARF in the compile unit that contains 0x114720 (not
sure if there is a lookup by address in llmv-dwarfdump?) and make sure there is
a DW_TAG_subprogram that contains this address.
Greg
> Ted
>
> --
> Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] fate of TimeValue
I am fine with TimeValue going away. I would love to just use STL std::chrono stuff if we can get away with it. If there is a bunch of code that gets re-written all of the time, then using the LLVM TimeValue class is fine if it is needed. Greg > On Oct 7, 2016, at 10:29 PM, Mehdi Amini via lldb-dev > wrote: > >> >> On Oct 7, 2016, at 10:19 PM, Pavel Labath wrote: >> >> On 7 October 2016 at 21:42, Mehdi Amini wrote: >>> On Oct 7, 2016, at 9:30 PM, Pavel Labath via lldb-dev wrote: The llvm-dev thread seems to have fizzed out - I would assume they are not interested in std::chrono. >>> >>> I suggest a totally different course of action: any utility (except >>> specific to the debugger for some reason) should be submitted into LLVM >>> (Support?). >>> I may be happy to have it available next months in LLVM, and I may not >>> think about looking in every subproject. >>> >>> The question is not if “they” (I rather have you guys say “we”) are not >>> interested, but rather “is anyone opposing to having utilities wrapping / >>> manipulating std::chrono in LLVM”. >>> >> >> I like that idea. I've added you to the reviews so you can see what >> kind of utility functions I am talking about. BTW, LLVM seems to have >> a TimeValue class as well (presumably because not all compilers used >> to support std::chrono) > > I believe TimeValue was created before std::chrono was standardized (first > committed in 2004!) > >> - one possibility would be to start using that >> instead, although I would prefer std::chrono. > > Indeed, I believe we tend to move to the standard version of our utilities > when the feature is complete in the compiler versions we support. > > It is also possible that not all of TimeValue features are supported by > std::chrono, I haven't compared in detail. > > — > Mehdi > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
I imagine that Hans doesn't have Python 3 installed on his system, so LLDB didn't autoconfigure with Python support. On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev < lldb-dev@lists.llvm.org> wrote: > > Does the 4.0 binary not work for you? It is the first release that contains > prebuilt lldb binary. > > Looks like the Python API is not included though. Do you know why it was > left out? > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
He said he did, so I don't know. Vadim, can you elaborate? When you run `lldb -P` from the command line, what do you see? On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I imagine that Hans doesn't have Python 3 installed on his system, so LLDB > didn't autoconfigure with Python support. > > On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > > Does the 4.0 binary not work for you? It is the first release that contains > prebuilt lldb binary. > > Looks like the Python API is not included though. Do you know why it was > left out? > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the 'site-packages' directory does not exist. Nor do I see '_lldb.pyd' anywhere else. 'script import lldb' also fails, of course. On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner wrote: > He said he did, so I don't know. Vadim, can you elaborate? When you run > `lldb -P` from the command line, what do you see? > > On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> I imagine that Hans doesn't have Python 3 installed on his system, so >> LLDB didn't autoconfigure with Python support. >> >> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >> > Does the 4.0 binary not work for you? It is the first release that contains >> prebuilt lldb binary. >> >> Looks like the Python API is not included though. Do you know why it >> was left out? >> >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
I may know what this is. Can you try setting PYTHONPATH though to point to your Python 3.5 installation though and see if it fixes it? (I don't think it will, but let's try anyway) On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov wrote: > It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the > 'site-packages' directory does not exist. Nor do I see '_lldb.pyd' > anywhere else. > 'script import lldb' also fails, of course. > > On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner > wrote: > > He said he did, so I don't know. Vadim, can you elaborate? When you run > `lldb -P` from the command line, what do you see? > > On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > I imagine that Hans doesn't have Python 3 installed on his system, so LLDB > didn't autoconfigure with Python support. > > On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > > Does the 4.0 binary not work for you? It is the first release that contains > prebuilt lldb binary. > > Looks like the Python API is not included though. Do you know why it was > left out? > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
Nope, that didn't help. On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner wrote: > I may know what this is. Can you try setting PYTHONPATH though to point > to your Python 3.5 installation though and see if it fixes it? (I don't > think it will, but let's try anyway) > > On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov wrote: > >> It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the >> 'site-packages' directory does not exist. Nor do I see '_lldb.pyd' >> anywhere else. >> 'script import lldb' also fails, of course. >> >> On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner >> wrote: >> >> He said he did, so I don't know. Vadim, can you elaborate? When you run >> `lldb -P` from the command line, what do you see? >> >> On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >> I imagine that Hans doesn't have Python 3 installed on his system, so >> LLDB didn't autoconfigure with Python support. >> >> On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >> > Does the 4.0 binary not work for you? It is the first release that contains >> prebuilt lldb binary. >> >> Looks like the Python API is not included though. Do you know why it >> was left out? >> >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> >> ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-3.8.1 prebuilt binary for windows7
I think it is a problem with the way we built lldb. I will look into what additional steps we need to take when making the prebuilt binary so that it works next time. On Tue, Oct 11, 2016 at 6:20 PM Vadim Chugunov wrote: > Nope, that didn't help. > > On Tue, Oct 11, 2016 at 5:16 PM, Zachary Turner > wrote: > > I may know what this is. Can you try setting PYTHONPATH though to point > to your Python 3.5 installation though and see if it fixes it? (I don't > think it will, but let's try anyway) > > On Tue, Oct 11, 2016 at 4:59 PM Vadim Chugunov wrote: > > It outputs 'c:\Program Files (x86)\LLVM\lib\site-packages', however the > 'site-packages' directory does not exist. Nor do I see '_lldb.pyd' > anywhere else. > 'script import lldb' also fails, of course. > > On Tue, Oct 11, 2016 at 4:01 PM, Zachary Turner > wrote: > > He said he did, so I don't know. Vadim, can you elaborate? When you run > `lldb -P` from the command line, what do you see? > > On Tue, Oct 11, 2016 at 4:00 PM Reid Kleckner via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > I imagine that Hans doesn't have Python 3 installed on his system, so LLDB > didn't autoconfigure with Python support. > > On Sun, Oct 9, 2016 at 1:07 PM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > > Does the 4.0 binary not work for you? It is the first release that contains > prebuilt lldb binary. > > Looks like the Python API is not included though. Do you know why it was > left out? > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > > > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
