History log of /external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
a224c7c673a433ef9f6673929a5eb8508bd8e73d 31-Jul-2013 Matt Kopec <Matt.Kopec@intel.com> Add the LD_LIBRARY_PATH to target.env-vars for tests expecting libimf.so when testing with ICC.

Patch from Andy Kaylor.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@187520 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
6475c42148a8ea1ca86e5db465db7eca742d897d 04-Dec-2012 Greg Clayton <gclayton@apple.com> <rdar://problem/12798131>

Cleaned up the option parsing code to always pass around the short options as integers. Previously we cast this down to "char" and lost some information. I recently added an assert that would detect duplicate short character options which was firing during the test suite.

This fix does the following:
- make sure all short options are treated as "int"
- make sure that short options can be non-printable values when a short option is not required or when an option group is mixed into many commands and a short option is not desired
- fix the help printing to "do the right thing" in all cases. Previously if there were duplicate short character options, it would just not emit help for the duplicates
- fix option parsing when there are duplicates to parse options correctly. Previously the option parsing, when done for an OptionGroup, would just start parsing options incorrectly by omitting table entries and it would end up setting the wrong option value



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@169189 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
99e8729597edabcc603fa41ccf8b80c1a8e58f4b 26-Nov-2012 Daniel Malea <daniel.malea@intel.com> Improvement to TestGlobalVariables fix
- use lldb settings command instead of os.environ
- use dyldPath fixture variable instead of hardcoding LD_LIBRARY_PATH
- add tear-down hook to restore environment after testcase is run



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168613 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
1565469cb10b1b870b4ea920297805e62d0e70e0 26-Nov-2012 Daniel Malea <daniel.malea@intel.com> Fix TestGlobalVariables.py (on Linux)
- setting LD_LIBRARY_PATH required for the test program to run correctly



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168595 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
431d839a33e9a274e705f7a268a1c9de2ffc2da2 22-Sep-2012 Jim Ingham <jingham@apple.com> 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!!!!!


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@164433 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
21b1984e161b0cadee331d32bfd721eccfdf4b1f 06-Apr-2012 Johnny Chen <johnny.chen@apple.com> Second batch of adding @dsym_test/@dwarf_test decorators to existing test cases.
Plus some minor cleanup of test method names.
Third and final batch is coming.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@154197 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
a1b9a90b7aef446302de9b845dc4f3b0e1473aa7 13-Nov-2011 Greg Clayton <gclayton@apple.com> <rdar://problem/10338439>

This is the actual fix for the above radar where global variables that weren't
initialized were not being shown correctly when leaving the DWARF in the .o
files. Global variables that aren't intialized have symbols in the .o files
that specify they are undefined and external to the .o file, yet document the
size of the variable. This allows the compiler to emit a single copy, but makes
it harder for our DWARF in .o files with the executable having a debug map
because the symbol for the global in the .o file doesn't exist in a section
that we can assign a fixed up linked address to, and also the DWARF contains
an invalid address in the "DW_OP_addr" location (always zero). This means that
the DWARF is incorrect and actually maps all such global varaibles to the
first file address in the .o file which is usually the first function. So we
can fix this in either of two ways: make a new fake section in the .o file
so that we have a file address in the .o file that we can relink, or fix the
the variable as it is created in the .o file DWARF parser and actually give it
the file address from the executable. Each variable contains a
SymbolContextScope, or a single pointer that helps us to recreate where the
variables came from (which module, file, function, etc). This context helps
us to resolve any file addresses that might be in the location description of
the variable by pointing us to which file the file address comes from, so we
can just replace the SymbolContextScope and also fix up the location, which we
would have had to do for the other case as well, and update the file address.
Now globals display correctly.

The above changes made it possible to determine if a variable is a global
or static variable when parsing DWARF. The DWARF emits a DW_TAG_variable tag
for each variable (local, global, or static), yet DWARF provides no way for
us to classify these variables into these categories. We can now detect when
a variable has a simple address expressions as its location and this will help
us classify these correctly.

While making the above changes I also noticed that we had two symbol types:
eSymbolTypeExtern and eSymbolTypeUndefined which mean essentially the same
thing: the symbol is not defined in the current object file. Symbol objects
also have a bit that specifies if a symbol is externally visible, so I got
rid of the eSymbolTypeExtern symbol type and moved all code locations that
used it to use the eSymbolTypeUndefined type.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@144489 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
1a78f6aa3f6896d0c7e5c7dd2926d7cc876bbf55 09-Aug-2011 Johnny Chen <johnny.chen@apple.com> Add a negative self.expect() to verify that the bug has been fixed.

rdar://problem/9747668


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@137129 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
46171ff3f39bc194c07f187683b3aac2dd7e781d 09-Jul-2011 Johnny Chen <johnny.chen@apple.com> Add rdar://problem/9747668 info for "target variable g_marked_spot.y" command.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@134772 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
457019507e85e0bf27ecff4438cdd3722cf81e97 09-Jul-2011 Johnny Chen <johnny.chen@apple.com> Add test scenarios for 'target variable' command into TestGlobalVariables.py file.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@134771 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py
b8025be2976a40d072e9a6d4eb7c9316d65bb16e 25-Jun-2011 Johnny Chen <johnny.chen@apple.com> Move global_variables dir to lang/c and foundation dir to lang/objc.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@133883 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/lang/c/global_variables/TestGlobalVariables.py