- May 24, 2013
-
-
Sean Callanan authored
Scalar now can make itself signed if needed. <rdar://problem/13977632> llvm-svn: 182668
-
Ashok Thirumurthi authored
which takes a first step towards symbolization of disassembled instructions. llvm-svn: 182650
-
rdar://problem/13643315Greg Clayton authored
Fixed performance issues that arose after changing SBTarget, SBProcess, SBThread and SBFrame over to using a std::shared_ptr to a ExecutionContextRef. The ExecutionContextRef doesn't store a std::weak_ptr to a stack frame because stack frames often get replaced with new version, so it held onto a StackID object that would allow us to ask the thread each time for the frame for the StackID. The linear function was too slow for large recursive stacks. We also fixed an issue where anytime the std::shared_ptr<ExecutionContextRef> in any SBTarget, SBProcess, SBThread objects was turned into an ExecutionContext object, it would try to resolve all items in the ExecutionContext which are shared pointers. Even if the StackID in the ExecutionContextRef was invalid, it was looking through all frames in every thread. This causes a lot of unnecessary frame accesses. llvm-svn: 182627
-
Filipe Cabecinhas authored
llvm-svn: 182619
-
- May 23, 2013
-
-
Michael Sartain authored
Which means "platform process list" should work and list the architecture. We are now parsing the elf build-id if it exists, which should allow us to load stripped symbols (looking at that next). llvm-svn: 182610
-
Michael Sartain authored
settings set use-color [false|true] settings set prompt "${ansi.bold}${ansi.fg.green}(lldb)${ansi.normal} " also "--no-use-colors" on the command prompt llvm-svn: 182609
-
rdar://problem/13966084Greg Clayton authored
Make sure to not call "regexec" from <regex.h> with a NULL C string, otherwise we can crash. llvm-svn: 182607
-
Greg Clayton authored
llvm-svn: 182540
-
Greg Clayton authored
llvm-svn: 182538
-
Greg Clayton authored
llvm-svn: 182537
-
Greg Clayton authored
Added logging for the OS plug-in python objects in OperatingSystemPython so we can see the python dictionary returned from the plug-in when logging is enabled. llvm-svn: 182530
-
Sean Callanan authored
live as long as they needed to. This led to equality tests involving persistent variables often failing or succeeding when they had no business doing so. To do this, I introduced the ability for a memory allocation to "leak" - that is, to persist in the process beyond the lifetime of the expression. Hand-declared persistent variables do this now. <rdar://problem/13956311> llvm-svn: 182528
-
- May 22, 2013
-
-
rdar://problem/13956179Greg Clayton authored
Fixed ProcessMachCore to be able to locate the main executeable in the core file even if it doesn't start at a core file address range boundary. Prior to this we only checked the first bytes of each range in the core file for mach_kernel or dyld. Now we still do this, but if we don't find the mach_kernel or dyld anywhere, we go through all core file ranges and check every 0x1000 to see if we can find dyld or the mach_kernel. Now that we can properly detect the mach_kernel at any address, we don't need to call "DynamicLoaderDarwinKernel::SearchForDarwinKernel(Process*)" anymore. llvm-svn: 182513
-
rdar://problem/13880690Greg Clayton authored
Lock the lldb_private::Module mutex while tearing down the module to make sure we don't get clients accessing the contents on a module as it is going away. llvm-svn: 182511
-
rdar://problem/13455021Greg Clayton authored
Another fix to make sure that if we aren't able to extract an object file for any reason, we don't crash when trying to parse the debug map info. llvm-svn: 182441
-
rdar://problem/13455021Greg Clayton authored
lldb crashes with universal file containing skinny BSD archives when doing DWARF with .o file debugging. llvm-svn: 182437
-
Enrico Granata authored
llvm-svn: 182434
-
- May 21, 2013
-
-
Greg Clayton authored
Added a test case that verifies that LLDB can debug across a process exec'ing itself into a new program. This currently is only enabled for Darwin since we exec from 64 bit to 32 bit and vice versa for 'x86_64' targets. This can easily be adapted for linux and other platforms, but I didn't want to break any buildbots by assuming it will work. llvm-svn: 182428
-
rdar://problem/13878726Enrico Granata authored
Yet another implementation of the python in dSYM autoload :) This time we are going with a ternary setting: true - load, do not warn false - do not load, do not warn warn - do not load, warn (default) llvm-svn: 182414
-
rdar://problem/13925432Enrico Granata authored
A user request such as: memory read -fc -s10 -c1 *charPtrPtr would cause us to crash upon trying to read 1 char of size 10 from memory This request is now translated into: memory read -fc -s1 -c10 *charPtrPtr (i.e. read 10 chars of size 1 from memory) which is probably also what the user originally wanted llvm-svn: 182398
-
rdar://problem/13892516Greg Clayton authored
LLDB can now debug across calls to exec when the architecture changes from say i386 to x86_64 (on darwin). llvm-svn: 182345
-
Enrico Granata authored
Thanks to Greg Clayton for catching this llvm-svn: 182339
-
Enrico Granata authored
There are two settings: target.load-script-from-symbol-file is a boolean that says load or no load (default: false) target.warn-on-script-from-symbol-file is also a boolean, it says whether you want to be warned when a script file is not loaded due to security (default: true) the auto loading on change for target.load-script-from-symbol-file is preserved llvm-svn: 182336
-
rdar://problem/13925626Enrico Granata authored
Correctly handle the case of a ValueObjectVariable backed by a Vector llvm-svn: 182330
-
rdar://problem/13925626Enrico Granata authored
Replacing an assertion with an error - at least we won’t crash llvm-svn: 182326
-
Enrico Granata authored
llvm-svn: 182325
-
rdar://problem/13878726Enrico Granata authored
This changes the setting target.load-script-from-symbol-file to be a ternary enum value: default (the default value) will NOT load the script files but will issue a warning suggesting workarounds yes will load the script files no will not load the script files AND will NOT issue any warning if you change the setting value from default to yes, that will then cause the script files to be loaded (the assumption is you didn't know about the setting, got a warning, and quickly want to remedy it) if you have a settings set command for this in your lldbinit file, be sure to change "true" or "false" into an appropriate "yes" or "no" value llvm-svn: 182323
-
- May 20, 2013
-
-
Greg Clayton authored
llvm-svn: 182302
-
Greg Clayton authored
llvm-svn: 182301
-
- May 18, 2013
-
-
Sean Callanan authored
the Objective-C object checker and the pointer checker) were not always installed into expressions. <rdar://problem/13882566> llvm-svn: 182183
-
rdar://problem/11398407Greg Clayton authored
Name matching was working inconsistently across many places in LLDB. Anyone doing name lookups where you want to look for all types of names should used "eFunctionNameTypeAuto" as the sole name type mask. This will ensure that we get consistent "lookup function by name" results. We had many function calls using as mask like "eFunctionNameTypeBase | eFunctionNameTypeFull | eFunctionNameTypeMethod | eFunctionNameTypeSelector". This was due to the function lookup by name evolving over time, but as it stands today, use eFunctionNameTypeAuto when you want general name lookups. Either ModuleList::FindFunctions() or Module::FindFunctions() will figure out the right kinds of names to lookup and remove the "eFunctionNameTypeAuto" and replace it with the exact subset of what the name can be. This checkin also changes eFunctionNameTypeAny over to use eFunctionNameTypeAuto to reflect this. llvm-svn: 182179
-
rdar://problem/13928053Enrico Granata authored
Fix the fact that an empty NSString (e.g. one obtained from @"" would show no summary) llvm-svn: 182173
-
Matt Kopec authored
Thus, this patch also negates a previous fix for handling SIGCHLD. llvm-svn: 182166
-
- May 17, 2013
-
-
Greg Clayton authored
Allow LLDB to be built on a system with an installed gcc/g++ that isn't the default. I recently installed gcc-4.7/g++-4.7 on Ubuntu and tried to build by specifying: CC=gcc-4.7 CXX=g++-4.7 as configure and make args, but it didn't work when being run with makefiles. This patch fixes that. llvm-svn: 182158
-
Daniel Malea authored
- copy lldb python module into directory specified with CMAKE_INSTALL_PREFIX - make liblldb.so a symlink (to liblldb.so.X.Y where X.Y is the LLVM version) llvm-svn: 182157
-
Matt Kopec authored
-Remove tracing of fork/vfork until we add support for tracing inferiors' children on Linux. -Add trace exec option for ptrace so that we don't receive legacy SIGTRAP signals on execve calls. -Add handling of SIGCHLD sent by kernel (for now, deliver the signal to the inferior). llvm-svn: 182153
-
Michael Sartain authored
Comment out ObjectFileELF::GetModuleSpecifications() function until I can debug where it's causing tests to fail. llvm-svn: 182069
-
Jim Ingham authored
rdar://problem/13916722 llvm-svn: 182068
-
rdar://problem/13217784Greg Clayton authored
"source list -n <func>" can now show more than one location that matches a function name. It will unique multiple of the same source locations so they don't get displayed. It also handles inline functions correctly. llvm-svn: 182067
-
rdar://problem/13893094Greg Clayton authored
Show variables that were in the debug info but optimized out. Also display a good error message when one of these variables get used in an expression. llvm-svn: 182066
-