Re: [lldb-dev] Bug with ThreadPlanStepRange::InRange, symbol context and target.source-map setting

2016-05-09 Thread Jim Ingham via lldb-dev
I talked with Greg about this before I posted the suggestion below, and having the LineEntry contain both mapped and unmapped FileSpec's was his suggestion... But who knows what changes of heart a weekend might bring. Jim > On May 9, 2016, at 9:43 AM, Ted Woodward wrote: > > I'll defer to Gr

Re: [lldb-dev] Loading debug symbols (C++, Ubuntu 14.04)

2016-05-09 Thread Greg Clayton via lldb-dev
> I also checked the current HEAD of the lldb source tree to see if there are > any changes, compared with my older revision. There is only a slight > difference in how Symbols::LoadExecutableSymbolFile uses the /usr/lib/debug > directory: > > // Some debug files may stored in the module direct

Re: [lldb-dev] Bug with ThreadPlanStepRange::InRange, symbol context and target.source-map setting

2016-05-09 Thread Ted Woodward via lldb-dev
I'll defer to Greg on remapping FileSpecs in SymbolContexts - he's the one who added it, in r168845: commit 214d2a327feb2e5987d093c2b63c457ffbd1d677 Author: Greg Clayton Date: Thu Nov 29 00:53:06 2012 + Make stack frames fix up their line table entries when the target has s

[lldb-dev] [Bug 27687] New: We cannot backtrace out of fflush() on Linux x86_64

2016-05-09 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27687 Bug ID: 27687 Summary: We cannot backtrace out of fflush() on Linux x86_64 Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal

Re: [lldb-dev] Loading debug symbols (C++, Ubuntu 14.04)

2016-05-09 Thread Stefan Kratochwil via lldb-dev
Hi Pavel, I stepped through SymbolVendorELF::CreateInstance(), and it seems that the problem lies within Symbols::LocateExecutableSymbolFile (Host/common/Symbols.cpp). This method looks at the correct locations: (gdb) print debug_file_search_paths $35 = {m_files = std::vector of length 3, cap

Re: [lldb-dev] Loading debug symbols (C++, Ubuntu 14.04)

2016-05-09 Thread Pavel Labath via lldb-dev
You can also use SBCommandInterpreter::HandleCommand, which gives you a bit more control over what happens. good luck with your thesis. pl On 9 May 2016 at 10:00, Stefan Kratochwil wrote: > Hi Pavel, > > thanks for your quick reply. I am currently using a release build, so it may > take a momen

Re: [lldb-dev] Loading debug symbols (C++, Ubuntu 14.04)

2016-05-09 Thread Stefan Kratochwil via lldb-dev
Hi Pavel, thanks for your quick reply. I am currently using a release build, so it may take a moment until I can step through there. I'll report back as soon as possible (my masters thesis somehow depends on that ;) ). I was just about to implement an addon for the API tonight, when I found

Re: [lldb-dev] Loading debug symbols (C++, Ubuntu 14.04)

2016-05-09 Thread Pavel Labath via lldb-dev
Hi Stefan, what you are describing should work out of the box, so the fact that you are having to add the symbols manually is a bug. I haven't tried it with the apache binary specifically, but lldb can certainly find external debug symbols for libc (definitely on ubuntu 14.04, as that's what I use