- Sep 22, 2012
-
-
Jim Ingham authored
Fix all the test case breakages caused by folks writing tests all over the place that depended explicitly on the output of "break set". Please don't do this sort of thing!!!!! llvm-svn: 164433
-
- Sep 21, 2012
-
-
Enrico Granata authored
This feature allows us to group test cases into logical groups (categories), and to only run a subset of test cases based on these categories. Each test-case can have a new method getCategories(self): which returns a list of strings that are the categories to which the test case belongs. If a test-case does not provide its own categories, we will look for categories in the class that contains the test case. If that fails too, the default implementation looks for a .category file, which contains a comma separated list of strings. The test suite will recurse look for .categories up until the top level directory (which we guarantee will have an empty .category file). The driver dotest.py has a new --category <foo> option, which can be repeated, and specifies which categories of tests you want to run. (example: ./dotest.py --category objc --category expression) All tests that do not belong to any specified category will be skipped. Other filtering options still exist and should not interfere with category filtering. A few tests have been categorized. Feel free to categorize others, and to suggest new categories that we could want to use. All categories need to be validly defined in dotest.py, or the test suite will refuse to run when you use them as arguments to --category. In the end, failures will be reported on a per-category basis, as well as in the usual format. This is the very first stage of this feature. Feel free to chime in with ideas for improvements! llvm-svn: 164403
-
- Sep 18, 2012
-
-
-
rdar://problem/11988289Enrico Granata authored
<rdar://problem/11988289> Making C++ synthetic children provider for NSDictionary and related classes llvm-svn: 164144
-
- Sep 13, 2012
-
-
rdar://problem/11086338Enrico Granata authored
<rdar://problem/11086338> Implementing support for synthetic children generated by running C++ code instead of Python scripts ; Adding a bunch of value-generating APIs to our private code layer ; Providing synthetic children for NSArray llvm-svn: 163818
-
- Sep 11, 2012
-
-
Jim Ingham authored
Shortcut ThreadPlanStepRange::MischiefManaged - if we have pushed new plans and they are not done, then we aren't done either. <rdar://problem/12259124> llvm-svn: 163572
-
- Sep 08, 2012
-
-
Jim Ingham authored
llvm-svn: 163436
-
- Sep 04, 2012
-
-
rdar://problem/11485744Enrico Granata authored
<rdar://problem/11485744> Implement important data formatters in C++. Have the Objective-C language runtime plugin expose class descriptors objects akin to the objc_runtime.py Pythonic implementation. Rewrite the data formatters for some core Cocoa classes in C++ instead of Python. llvm-svn: 163155
-
- Aug 29, 2012
-
-
rdar://problem/11757916Greg Clayton authored
Make breakpoint setting by file and line much more efficient by only looking for inlined breakpoint locations if we are setting a breakpoint in anything but a source implementation file. Implementing this complex for a many reasons. Turns out that parsing compile units lazily had some issues with respect to how we need to do things with DWARF in .o files. So the fixes in the checkin for this makes these changes: - Add a new setting called "target.inline-breakpoint-strategy" which can be set to "never", "always", or "headers". "never" will never try and set any inlined breakpoints (fastest). "always" always looks for inlined breakpoint locations (slowest, but most accurate). "headers", which is the default setting, will only look for inlined breakpoint locations if the breakpoint is set in what are consudered to be header files, which is realy defined as "not in an implementation source file". - modify the breakpoint setting by file and line to check the current "target.inline-breakpoint-strategy" setting and act accordingly - Modify compile units to be able to get their language and other info lazily. This allows us to create compile units from the debug map and not have to fill all of the details in, and then lazily discover this information as we go on debuggging. This is needed to avoid parsing all .o files when setting breakpoints in implementation only files (no inlines). Otherwise we would need to parse the .o file, the object file (mach-o in our case) and the symbol file (DWARF in the object file) just to see what the compile unit was. - modify the "SymbolFileDWARFDebugMap" to subclass lldb_private::Module so that the virtual "GetObjectFile()" and "GetSymbolVendor()" functions can be intercepted when the .o file contenst are later lazilly needed. Prior to this fix, when we first instantiated the "SymbolFileDWARFDebugMap" class, we would also make modules, object files and symbol files for every .o file in the debug map because we needed to fix up the sections in the .o files with information that is in the executable debug map. Now we lazily do this in the DebugMapModule::GetObjectFile() Cleaned up header includes a bit as well. llvm-svn: 162860
-
- Aug 24, 2012
-
-
Johnny Chen authored
Add 'attach <pid>|<process-name>' command to lldb, as well as 'detach' which is an alias of 'process detach'. Add two completion test cases for "attach" and "detach". llvm-svn: 162573
-
Johnny Chen authored
Previously we put a WatchpointSentry object within StopInfo.cpp to disable-and-then-enable the watchpoint itself while we are performing the actions associated with the triggered watchpoint, which can cause the user-initiated watchpoint disabling action to be negated. Add a test case to verify that a watchpoint can be disabled during the callbacks. llvm-svn: 162483
-
- Aug 23, 2012
-
-
Johnny Chen authored
llvm-svn: 162467
-
Johnny Chen authored
Make a test scenario stronger, since, by default, the setting interpreter.expand-regex-aliases is false. llvm-svn: 162465
-
Johnny Chen authored
llvm-svn: 162462
-
Johnny Chen authored
Make it so that "b 245" should set a breakpoint at line 245 of the current file. Also add a simple test file. llvm-svn: 162419
-
- Aug 22, 2012
-
-
Greg Clayton authored
Reimplemented the code that backed the "settings" in lldb. There were many issues with the previous implementation: - no setting auto completion - very manual and error prone way of getting/setting variables - tons of code duplication - useless instance names for processes, threads Now settings can easily be defined like option values. The new settings makes use of the "OptionValue" classes so we can re-use the option value code that we use to set settings in command options. No more instances, just "does the right thing". llvm-svn: 162366
-
- Aug 16, 2012
-
-
Johnny Chen authored
Add an lldb command line option to specify a core file: --core/-c. For consistency, change the "target create" command to also use --core. llvm-svn: 161993
-
- Aug 14, 2012
-
-
Johnny Chen authored
When trying to take snapshots of a watched variable, if the frame is unable to evaluate the variable expression, do not take the sanpshot and forget about the stop info. It is possible that the variable expression has gone out of scope, we'll revise the hit count due to the false alarms. llvm-svn: 161892
-
rdar://problem/11589605Enrico Granata authored
'type category enable *' command to match 'type category disable *' llvm-svn: 161882
-
Johnny Chen authored
Change the test case, too. llvm-svn: 161806
-
- Aug 13, 2012
-
-
Johnny Chen authored
Record the snapshot of our watched value when the watchpoint is set or hit. And report the old/new values when watchpoint is triggered. Add some test scenarios. llvm-svn: 161785
-
- Aug 11, 2012
-
-
Jim Ingham authored
the currently selected thread. <rdar://problem/10458225> llvm-svn: 161723
-
- Aug 10, 2012
-
-
Johnny Chen authored
llvm-svn: 161684
-
rdar://problem/11457143Johnny Chen authored
Add 'watchpoint command add/delete/list' to lldb, plus two .py test files. llvm-svn: 161638
-
rdar://problem/11578397Enrico Granata authored
<rdar://problem/11578397> Adding a new --summary-string option for the frame variable command which allows the user to provide a summary string with which he wants to display the variables without having to make a named summary first llvm-svn: 161623
-
- Aug 09, 2012
-
-
Jim Ingham authored
<rdar://problem/11703715> llvm-svn: 161611
-
rdar://problem/10449092Enrico Granata authored
<rdar://problem/10449092> Adding a new uppercase hex format specifier. This commit also changes the short names for formats so that uppercase hex can be 'X', which was previously assigned to hex float. hex float now has no short name. llvm-svn: 161606
-
Sean Callanan authored
an expected failure. llvm-svn: 161556
-
rdar://problem/12061386Enrico Granata authored
<rdar://problem/12061386> Fixing data-formatter-cpp test case - previous version had an unfortunate dependency on the value of uninitialized memory llvm-svn: 161555
-
Sean Callanan authored
them as expected failures until they are fixed. llvm-svn: 161547
-
- Aug 08, 2012
-
-
rdar://problem/11975483Enrico Granata authored
<rdar://problem/11975483> Removing user-visible references to 'dict' as a parameter name for Python summary-generating functions since it is a Python keyword. llvm-svn: 161467
-
- Jul 25, 2012
-
-
Filipe Cabecinhas authored
Make git not delete some empty dirs. Otherwise a git checkout would be different from an svn checkout. llvm-svn: 160717
-
- Jul 19, 2012
-
-
Filipe Cabecinhas authored
Make git not delete my_working_dir. Otherwise a git checkout would be different from an svn checkout. llvm-svn: 160506
-
- Jul 13, 2012
-
-
- Jul 12, 2012
-
-
Filipe Cabecinhas authored
path passed with -w Test this functionality. llvm-svn: 160130
-
- Jun 29, 2012
-
-
- Jun 20, 2012
-
-
Filipe Cabecinhas authored
Adds a utility class method to TestBase that checks and removes a temp file. Removed every use of system() to execute rm -f. llvm-svn: 158809
-
- Jun 19, 2012
-
-
Johnny Chen authored
Test suite cleanup: use Python API to remove files as part of cleanup instead of running OS commands. llvm-svn: 158737
-