summaryrefslogtreecommitdiffstats
path: root/lldb
Commit message (Collapse)AuthorAgeFilesLines
...
* Patch from Daniel Dunbar for future-proof against ↵Johnny Chen2011-11-292-0/+22
| | | | | | http://llvm.org/viewvc/llvm-project?view=rev&revision=145331. llvm-svn: 145345
* Changed ClangASTImporter to allow finer-grainedSean Callanan2011-11-293-3/+38
| | | | | | | | management of what allocations remain after an expression finishes executing. This saves around 2.5KiB per expression for simple expressions. llvm-svn: 145342
* Added some documentation on the new GDB remote packets we have added and useGreg Clayton2011-11-281-0/+491
| | | | | | in LLDB. llvm-svn: 145314
* SBProcess.PutSTDIN() needs to be properly typemapped when swigging,Johnny Chen2011-11-287-1/+100
| | | | | | | | | | | | | | | | | so that we can do Python scripting like this: target = self.dbg.CreateTarget(self.exe) self.dbg.SetAsync(True) process = target.LaunchSimple(None, None, os.getcwd()) process.PutSTDIN("Line 1 Entered.\n") process.PutSTDIN("Line 2 Entered.\n") process.PutSTDIN("Line 3 Entered.\n") Add TestProcessIO.py to exercise the process IO API: PutSTDIN()/GetSTDOUT()/GetSTDERR(). llvm-svn: 145282
* Clarify the SBProcess Python API GetSTDOUT()/GetSTDERR(). They look ↵Johnny Chen2011-11-281-0/+10
| | | | | | | | different from the C++ API due to swig typemapping. llvm-svn: 145260
* <rdar://problem/10413589>Greg Clayton2011-11-281-19/+22
| | | | | | | Fixed a potential crasher where we weren't checking we got a valid DIE in a compile unit. llvm-svn: 145226
* Fixed an issue where we might cause our test suite to exit if we end upGreg Clayton2011-11-281-1/+1
| | | | | | | concatenating a string with "None" in python. Using a python format string gets us around this by handling it gracefully. llvm-svn: 145225
* Now the linux platform lets it be known that it can't launch processes forGreg Clayton2011-11-281-0/+6
| | | | | | debugging. llvm-svn: 145221
* CommandObjectProcess was recently changed to automatically use the platformGreg Clayton2011-11-2811-112/+417
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to launch a process for debugging. Since this isn't supported on all platforms, we need to do what we used to do if this isn't supported. I added: bool Platform::CanDebugProcess (); This will get checked before trying to launch a process for debugging and then fall back to launching the process through the current host debugger. This should solve the issue for linux and keep the platform code clean. Centralized logging code for logging errors, warnings and logs when reporting things for modules or symbol files. Both lldb_private::Module and lldb_private::SymbolFile now have the following member functions: void LogMessage (Log *log, const char *format, ...); void ReportWarning (const char *format, ...); void ReportError (const char *format, ...); These will all output the module name and object (if any) such as: "error: lldb.so ...." "warning: my_archive.a(foo.o) ...." This will keep the output consistent and stop a lot of logging calls from having to try and output all of the information that uniquely identifies a module or symbol file. Many places in the code were grabbing the path to the object file manually and if the module represented a .o file in an archive, we would see log messages like: error: foo.a - some error happened llvm-svn: 145219
* Fixed an issue in the DWARFLocationList::Dump() function where default Greg Clayton2011-11-282-2/+8
| | | | | | | arguments were quietly masked as the code changed (modified version of a path from Dawn). llvm-svn: 145216
* Remove incorrect return type from SetHeaderDataByteSize accessor (partialGreg Clayton2011-11-281-1/+1
| | | | | | patch from Dawn). llvm-svn: 145212
* Shrink-to-fit our std::vector<DWARFDebugInfoEntry> collections and save 20%Greg Clayton2011-11-223-8/+16
| | | | | | | to 30% of memory. The size doubling was killing us and we ended up with up to just under 50% of empty capacity. Cleaning this up saves us a ton of memory. llvm-svn: 145086
* Got the sizeof(lldb_private::Symbol) down to 64 bytes (from 72 bytes) by notGreg Clayton2011-11-222-21/+21
| | | | | | | having the enumeration take up 32 bits for the type and by putting it into the bitfields that were already being used. llvm-svn: 145084
* 12% allocated memory savings when debugging clang with DWARF in .o files byGreg Clayton2011-11-222-0/+13
| | | | | | making sure we perfectly size our vector of symbols on the symbol table. llvm-svn: 145069
* <rdar://problem/10033754>Greg Clayton2011-11-221-2/+2
| | | | | | | | | Fixed an issue with the options for memory read where --count couldn't be used with the --binary option when writing data to a file. Also removed the GDB format option from the --binary version of memory read. llvm-svn: 145067
* Save the arguments for a process launch in the target.run-args so they canGreg Clayton2011-11-211-0/+3
| | | | | | easily be used in the next run. llvm-svn: 145051
* Many GDB users always want to display disassembly when they stop by using Greg Clayton2011-11-213-90/+261
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | something like "display/4i $pc" (or something like this). With LLDB we already were showing 3 lines of source before and 3 lines of source after the current source line when showing a stop context. We now improve this by allowing the user to control the number of lines with the new "stop-line-count-before" and "stop-line-count-after" settings. Also, there is a new setting for how many disassembly lines to show: "stop-disassembly-count". This will control how many source lines are shown when there is no source or when we have no source line info. settings set stop-line-count-before 3 settings set stop-line-count-after 3 settings set stop-disassembly-count 4 settings set stop-disassembly-display no-source The default values are set as shown above and allow 3 lines of source before and after (what we used to do) the current stop location, and will display 4 lines of disassembly if the source is not available or if we have no debug info. If both "stop-source-context-before" and "stop-source-context-after" are set to zero, this will disable showing any source when stopped. The "stop-disassembly-display" setting is an enumeration that allows you to control when to display disassembly. It has 3 possible values: "never" - never show disassembly no matter what "no-source" - only show disassembly when there is no source line info or the source files are missing "always" - always show disassembly. llvm-svn: 145050
* Update ProcessMonitor::MonitorCallback signature.Peter Collingbourne2011-11-212-1/+2
| | | | llvm-svn: 145021
* Update PlatformLinux::Attach signature.Peter Collingbourne2011-11-212-3/+3
| | | | llvm-svn: 145020
* Pulled in a new revision of LLVM/Clang and addedSean Callanan2011-11-1912-76/+155
| | | | | | | | | | | | | several patches. These patches fix a problem where templated types were not being completed the first time they were used, and fix a variety of minor issues I discovered while fixing that problem. One of the previous local patches was resolved in the most recent Clang, so I removed it. The others will be removed in due course. llvm-svn: 144984
* Further performance improvements in the DWARF parser:Greg Clayton2011-11-195-138/+135
| | | | | | | | | 1 - the DIE collections no longer have the NULL tags which saves up to 25% of the memory on typical C++ code 2 - faster parsing by not having to run the SetDIERelations() function anymore it is done when parsing the DWARF very efficiently. llvm-svn: 144983
* Ensure that the empty RecordDecl generated forSean Callanan2011-11-191-2/+6
| | | | | | | templates is properly complete (though still empty). llvm-svn: 144982
* Handle stepping through a trampoline where the jump target is calculated a ↵Jim Ingham2011-11-195-31/+149
| | | | | | | | | | runtime - and so doesn't match the name of the PLT entry. This solution assumes a naming convention agreed upon by us and the system folks, and isn't general. The general solution requires actually finding & calling the resolver function if it hasn't been called yet. That's more tricky. llvm-svn: 144981
* Added optional calls to lldb_private::Process for getting memory region infoGreg Clayton2011-11-1817-56/+292
| | | | | | | | | | | | | | | | | | | | | | | from a process and hooked it up to the new packet that was recently added to our GDB remote executable named debugserver. Now Process has the following new calls: virtual Error Process::GetMemoryRegionInfo (lldb::addr_t load_addr, MemoryRegionInfo &range_info); virtual uint32_t GetLoadAddressPermissions (lldb::addr_t load_addr); Only the first one needs to be implemented by subclasses that can add this support. Cleaned up the way the new packet was implemented in debugserver to be more useful as an API inside debugserver. Also found an error where finding a region for an address actually will pick up the next region that follows the address in the query so we also need ot make sure that the address we requested the region for falls into the region that gets returned. llvm-svn: 144976
* Looking at our memory usage with Instruments when debugging a large applicationGreg Clayton2011-11-184-286/+131
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | we say that the vectors of DWARFDebugInfoEntry objects were the highest on the the list. With these changes we cut our memory usage by 40%!!! I did this by reducing the size of the DWARFDebugInfoEntry from a previous: uint32_t offset uint32_t parent_idx uint32_t sibling_idx Abbrev * abbrev_ptr which was 20 bytes, but rounded up to 24 bytes due to alignment. Now we have: uint32_t offset uint32_t parent_idx uint32_t sibling_idx uint32_t abbr_idx:15, // 32767 possible abbreviation codes has_children:1, // 0 = no children, 1 = has children tag:16; // DW_TAG_XXX value This gets us down to 16 bytes per DIE. I tested some VERY large DWARF files (900MB) and found there were only ~700 unique abbreviations, so 32767 should be enough for any sane compiler. If it isn't there are built in assertions that will fire off and tell us. llvm-svn: 144975
* This commit completes the rearchitecting of ClangASTSourceSean Callanan2011-11-188-51/+261
| | | | | | | | | | | | | | | | | | | | | to allow variables in the persistent variable store to know how to complete themselves from debug information. That fixes a variety of bugs during dematerialization of expression results and also makes persistent variable and result variables ($foo, $4, ...) more useful. I have also added logging improvements that make it much easier to figure out how types are moving from place to place, and made some checking a little more aggressive. The commit includes patches to Clang which are currently being integrated into Clang proper; once these fixes are in Clang top-of-tree, these patches will be removed. The patches don't fix API; rather, they fix some internal bugs in Clang's ASTImporter that were exposed when LLDB was moving types from place to place multiple times. llvm-svn: 144969
* Redirect the stderr output into a file so as to not pollute the terminal.Johnny Chen2011-11-181-3/+8
| | | | llvm-svn: 144958
* Do not print debug messages if self.TraceON() is False.Johnny Chen2011-11-181-4/+10
| | | | llvm-svn: 144945
* Add a simple progress bar when neither '-v' nor '-t' is specified.Johnny Chen2011-11-181-5/+22
| | | | llvm-svn: 144940
* Use a pseudoterminal for local processes if no STDIO redirection or otherGreg Clayton2011-11-175-32/+51
| | | | | | file actions have been specified. llvm-svn: 144922
* Add an option '-S' to skip the build and cleanup while running the test.Johnny Chen2011-11-172-12/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use this option with care as you would need to build the inferior(s) by hand and build the executable(s) with the correct name(s). This option can be used with '-# n' to stress test certain test cases for n number of times. An example: [11:55:11] johnny:/Volumes/data/lldb/svn/trunk/test/python_api/value $ ls Makefile TestValueAPI.pyc linked_list TestValueAPI.py change_values main.c [11:55:14] johnny:/Volumes/data/lldb/svn/trunk/test/python_api/value $ make EXE=test_with_dsym clang -gdwarf-2 -O0 -arch x86_64 -c -o main.o main.c clang -gdwarf-2 -O0 -arch x86_64 main.o -o "test_with_dsym" /usr/bin/dsymutil -o "test_with_dsym.dSYM" "test_with_dsym" [11:55:20] johnny:/Volumes/data/lldb/svn/trunk/test/python_api/value $ cd ../.. [11:55:24] johnny:/Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v -# 10 -S -f ValueAPITestCase.test_with_dsym LLDB build dir: /Volumes/data/lldb/svn/trunk/build/Debug LLDB-89 Path: /Volumes/data/lldb/svn/trunk URL: https://johnny@llvm.org/svn/llvm-project/lldb/trunk Repository Root: https://johnny@llvm.org/svn/llvm-project Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 Revision: 144914 Node Kind: directory Schedule: normal Last Changed Author: gclayton Last Changed Rev: 144911 Last Changed Date: 2011-11-17 09:22:31 -0800 (Thu, 17 Nov 2011) Session logs for test failures/errors/unexpected successes will go into directory '2011-11-17-11_55_29' Command invoked: python ./dotest.py -v -# 10 -S -f ValueAPITestCase.test_with_dsym ---------------------------------------------------------------------- Collected 1 test 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 1.163s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.200s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.198s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.199s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.239s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 1.215s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.105s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.098s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.195s OK 1: test_with_dsym (TestValueAPI.ValueAPITestCase) Exercise some SBValue APIs. ... ok ---------------------------------------------------------------------- Ran 1 test in 1.197s OK [11:55:34] johnny:/Volumes/data/lldb/svn/trunk/test $ llvm-svn: 144919
* Now that I fixed the uninitialized callback problem, I can enable GCD pidGreg Clayton2011-11-172-17/+10
| | | | | | monitoring on darwin in the host layer. llvm-svn: 144918
* Rename test class appropriately.Johnny Chen2011-11-171-1/+1
| | | | llvm-svn: 144915
* Bumped Xcode project versions for lldb-89 and debugserver-153.Greg Clayton2011-11-173-22/+22
| | | | llvm-svn: 144911
* Fixed the issue that was causing our monitor process threads to crash, it Greg Clayton2011-11-176-9/+67
| | | | | | | | | | turned out to be unitialized data in the ProcessLaunchInfo default constructor. Turning on MallocScribble in the environment helped track this down. When we launch and attach using the host layer, we now inform the process that it shouldn't detach when by calling an accessor. llvm-svn: 144882
* Fixed an issue with the pthread_setspecific() where we weren't NULL-ing outGreg Clayton2011-11-177-25/+69
| | | | | | | | | | | | the thread specific data and were destroying the thread specfic data more than once. Also added the ability to ask a lldb::StateType if it is stopped with an additional paramter of "must_exist" which means that the state must be a stopped state for a process that still exists. This means that eStateExited and eStateUnloaded will no longer return true if "must_exist" is set to true. llvm-svn: 144875
* (no commit message)Jim Ingham2011-11-171-1/+1
| | | | llvm-svn: 144874
* Docstring clarification.Johnny Chen2011-11-161-1/+1
| | | | llvm-svn: 144848
* Also dump the pid of the process launching through the ↵Johnny Chen2011-11-161-0/+2
| | | | | | | | lldbtest.system(*popenargs, **kwargs) API. This helps track down possible zombie processes. llvm-svn: 144846
* Added support to the ASTImporter for passingSean Callanan2011-11-162-3/+39
| | | | | | | | | | | | | | | | | | completion information between different AST contexts. It works like this: - If a Decl is imported from a context that has completion metadata, then that Decl is associated with the same completion information (possibly none) as the Decl it was imported from. - If a Decl is imported from a context that does not have completion metadata, then it is marked as completable by consulting the Decl and context it was imported from. llvm-svn: 144838
* Changed the ClangASTImporter to store metadataSean Callanan2011-11-162-52/+101
| | | | | | | | | | | | | | | | for each AST context it knows about in a single object. This makes it faster to look up the appropriate ASTImpoter for a given ASTContext pair and also makes it much easier to delete all metadata for a given AST context. In the future, this fix will allow the ClangASTImporter to propagate completion information between the metadata for different AST contexts as its minions move AST objects around. llvm-svn: 144835
* Added a CopyType method to the ASTImporter thatSean Callanan2011-11-162-0/+13
| | | | | | handles opaque QualTypes. llvm-svn: 144813
* Remove invalid docstring (due to cut-and-paste error).Johnny Chen2011-11-161-1/+0
| | | | llvm-svn: 144807
* I made the ClangASTImporter owned by the targetSean Callanan2011-11-167-52/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rather than individually on behalf of each ASTContext. This allows the ASTImporter to know about all containers of types, which will let it be smarter about forwarding information about type origins. That means that the following sequence of steps will be possible (after a few more changes): - Import a type from a Module's ASTContext into an expression parser ASTContext, tracking its origin information -- this works now. - Because the result of the expression uses that type, import it from the expression parser ASTContext into the Target's scratch AST context, forwarding the origin information -- this needs to be added. - For a later expression that uses the result, import the type from the Target's scratch AST context, still forwarding origin information -- this also needs to be added. - Use the intact origin information to complete the type as needed -- this works now if the origin information is present. To this end, I made the following changes: - ASTImporter top-level copy functions now require both a source and a destination AST context parameter. - The ASTImporter now knows how to purge records related to an ASTContext that is going away. - The Target now owns and creates the ASTImporter whenever the main executable changes or (in the absence of a main executable) on demand. llvm-svn: 144802
* Made the darwin host layer properly reap any child processes that it spawns.Greg Clayton2011-11-169-87/+274
| | | | | | | | | | | | | | | | | | | | | | After recent changes we weren't reaping child processes resulting in many zombie processes. This was fixed by adding more settings to the ProcessLaunchOptions class that allow clients to specify a callback function and baton to be notified when their process dies. If one is not supplied a default callback will be used that "does the right thing". Cleaned up a race condition in the ProcessGDBRemote class that would attempt to monitor when debugserver died. Added an extra boolean to the process monitor callbacks that indicate if a process exited or not. If your process exited with a zero exit status and no signal, both items could be zero. Modified the process monitor functions to not require a callback function in order to reap the child process. llvm-svn: 144780
* Fixed a problem where the target didn't use aSean Callanan2011-11-162-11/+13
| | | | | | | | | | | | | | | NULL-terminated C string to store the contents of the expression prefix file. This meant that expressions, when printing the contents of the prefix into the expression's text, would invariably put in bad data after the end of the expression. Now, instead, we store the prefix contents in a std::string, which handles null-termination correctly. llvm-svn: 144760
* Fixed a crash when we merrily went on to try to logSean Callanan2011-11-161-0/+2
| | | | | | information about a nonexistent function declaration. llvm-svn: 144744
* Two fixes for Objetive-C methods that return structSean Callanan2011-11-162-3/+78
| | | | | | | | | | types. First, I added handling for the memset intrinsic in the IR, which is used to zero out the returned struct. Second, I fixed the object-checking instrumentation to objc_msgSend_stret, and generally tightened up how the object-checking functions get inserted. llvm-svn: 144741
* While we are at it, verify that 'my_int_ptr' points to 'g_my_int', using the ↵Johnny Chen2011-11-151-0/+6
| | | | | | | | SBTarget.ResolveLoadAddress() to get its SBAddress, and SBAddress.GetSymbol() to get the corresponding symbol. llvm-svn: 144728
* Fix objc runtime warnings from the inferior program.Johnny Chen2011-11-153-7/+9
| | | | llvm-svn: 144717
OpenPOWER on IntegriCloud