I am still seeing issues with source-level debugging. "target modules dump sections" has symbol entries. Also source level debugging is working in gdb, so I know that symbols are available. The strange thing is, I tried the same thing with a simple "Hello world" program and source level debugging worked. Both programs are being compiled with clang-3.4.
Can someone give me a tip where I can should put breakpoints in LLDB to debug this? Thanks, -Kal Am 8/7/13 12:04 AM, schrieb Kal Conley: > Hi Dan, > Sorry I wasn't clear. My fix fixes the test suite issue. The only > remaining issue is the source debugging issue. I haven't got to look > into that yet. I am on Debian Wheezy. > -Kal > > Am 8/6/13 11:44 PM, schrieb Malea, Daniel: >> Thank you Kal for the fix! Much appreciated :) >> >> I committed it in r187818. >> >> So, just to clarify, you're still unable to run the test suite after >> the fix? Which distro are you on? >> >> >> Thanks, >> Dan >> >> From: Kal Conley <[email protected] <mailto:[email protected]>> >> Date: Tuesday, 6 August, 2013 5:27 PM >> To: Andrew Kaylor <[email protected] >> <mailto:[email protected]>>, "[email protected] >> <mailto:[email protected]>" <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [lldb-dev] lldb problems on linux >> >> Hi Andy, >> So I figured out the python issue. Host::GetLLDBPath() is broken. It >> was failing for me because I am building in Release mode. It only >> works in Debug mode by luck :) The problem is lines 1035+ in >> source/Host/common/Host.cpp. llvm::Twine should only be used for >> temporary objects! See >> http://llvm.org/docs/ProgrammersManual.html#dss-twine >> >> I have attached a patch this fixes the issue. I haven't found time to >> investigate my other issue yet. >> >> Thanks! >> -Kal >> >> Am 8/6/13 4:29 PM, schrieb Kaylor, Andrew: >>> >>> Hmm… I’ve never seen the -P option print the wrong path. Looking >>> at the code (in Host::GetLLDBPath) it doesn’t even look possible for >>> it to print what you’re seeing. >>> >>> >>> >>> On the other hand, the second directory you mention should be the >>> correct one. If you set PYTHONPATH to that does “python -c ‘import >>> lldb’” work? >>> >>> >>> >>> -Andy >>> >>> >>> >>> *From:*Kal Conley [mailto:[email protected]] >>> *Sent:* Tuesday, August 06, 2013 2:00 AM >>> *To:* Kaylor, Andrew >>> *Cc:* [email protected] >>> *Subject:* Re: [lldb-dev] lldb problems on linux >>> >>> >>> >>> Hi Andy, >>> I tried >>> export PYTHONPATH=`$llvm/build/Debug+Asserts/bin/lldb -P` >>> but it didn't work for me. If I run `build/bin/lldb -P` it outputs >>> "build/lib7/site-packages" which doesn't exist. >>> There is a directory build/lib/python-2.7/site-packages but if I set >>> the PYTHONPATH to this directory I get the same errors. >>> >>> I can import lldb; in python successfully though. >>> >>> Any other ideas? >>> >>> -Kal >>> >>> >>> >>> 2013/8/5 Kaylor, Andrew <[email protected] >>> <mailto:[email protected]>> >>> >>> Hi Kal, >>> >>> >>> >>> For the second problem, you need to set the PYTHONPATH environment >>> variable. Try this: >>> >>> >>> >>> export PYTHONPATH=`$llvm/build/Debug+Asserts/bin/lldb -P` >>> >>> >>> >>> Regarding the source information, I would start by using the >>> following command within lldb (after you have created the target you >>> want to debug): >>> >>> >>> >>> target modules dump sections >>> >>> >>> >>> If you don’t see debug sections in that list, then that’s the >>> problem. If you do, try enabling DWARF logging (‘log enable dwarf >>> all’) and see if anything obvious turns up in the output when you >>> try to set a breakpoint. >>> >>> >>> >>> -Andy >>> >>> >>> >>> *From:*[email protected] >>> <mailto:[email protected]> >>> [mailto:[email protected] >>> <mailto:[email protected]>] *On Behalf Of *Kal Conley >>> *Sent:* Sunday, August 04, 2013 11:27 AM >>> *To:* [email protected] <mailto:[email protected]> >>> >>> >>> *Subject:* [lldb-dev] lldb problems on linux >>> >>> >>> >>> Hi, >>> >>> I recently build lldb from trunk (revision 187708) and source-level >>> debugging isn't working for me. It seems its not loading any source >>> information. What is the best way to troubleshoot this? >>> >>> Also make check-lldb doesn't work on Linux when building with CMake. >>> I just get error: >>> >>> This script requires lldb.py to be in either >>> /home/user/tools/llvm_3.4~svn187708/tools/lldb/build/Debug/LLDB.framework/Resources/Python, >>> /home/user/tools/llvm_3.4~svn187708/tools/lldb/build/Release/LLDB.framework/Resources/Python, >>> or >>> /home/user/tools/llvm_3.4~svn187708/tools/lldb/build/BuildAndIntegration/LLDB.framework/Resources/Python >>> >>> I get the same error with lldb-3.3. >>> >>> >>> >>> Thanks! >>> >>> >>> >> >
_______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
