| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue described in llvm.org/pr18065 is actually due to FreeBSD bug
theads/186309 [1], which is now fixed in FreeBSD SVN r261354 [2] and will
be merged to release branches shortly.
Diagnosed and fixed by John Wolfe.
[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=186309
[2] http://svnweb.freebsd.org/base?view=revision&revision=261354
llvm-svn: 200648
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes http://llvm.org/bugs/show_bug.cgi?id=18656.
Note this exposes a failure on Linux of
TestInferiorAssert.test_inferior_asserting_disassemble, similar to how
it fails on FreeBSD. I'll file a bug for this next. We're now getting
another frame beyond where we used to prior to this fix, so the fix is
exposing failures in previosly not-reachable frames.
Much thanks to Jason Molenda, who had much to do with helping figure
out where unwinding was breaking.
llvm-svn: 200600
|
|
|
|
|
|
|
|
|
|
|
|
| |
The many many benefits include:
1 - Input/Output/Error streams are now handled as real streams not a push style input
2 - auto completion in python embedded interpreter
3 - multi-line input for "script" and "expression" commands now allow you to edit previous/next lines using up and down arrow keys and this makes multi-line input actually a viable thing to use
4 - it is now possible to use curses to drive LLDB (please try the "gui" command)
We will need to deal with and fix any buildbot failures and tests and arise now that input/output and error are correctly hooked up in all cases.
llvm-svn: 200263
|
|
|
|
|
|
|
|
| |
ValueObjectPrinter could enter an infinite loop while trying to display an aptly formed ValueObject: a reference, with a child of some pointer type, such that the pointees chain ended up pointing back to some part of itself - a pointer to itself being the simplest such case
Fixed here by only setting a pointer depth when needed, and ensuring that we won't overflow and wrap the pointer depth when it's zero.
llvm-svn: 200247
|
|
|
|
|
|
|
|
| |
format should prevail over whatever format(s) a summary specifies
(see test case for an example)
llvm-svn: 199857
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The alias test "exprf x 1234" expands to "expr -f x 1234" and is
expected to fail: it ends up trying to evaluate the invalid expression
void
$__lldb_expr(void *$__lldb_arg)
{
-f x 1234;
}
On FreeBSD LLDB ends up finding a static function f() in a math library,
and thus the error produced does not include "use of undeclared
identifier 'f'".
We will report failure to parse the expression in any case, so require
only that error message.
llvm-svn: 199623
|
|
|
|
| |
llvm-svn: 199551
|
|
|
|
| |
llvm-svn: 199550
|
|
|
|
| |
llvm-svn: 199449
|
|
|
|
| |
llvm-svn: 199448
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part 1 changes PlatformLinux::CreateInstance to always create with
is_host=false; that method is only used as the plug-in creator method
associated with the remote-linux platform plugin, and should therefore
always be remote.
Part 1 patch by Steve Pucci.
Part 2: fix a test break on linux.
In test/functionalities/thread/thread_specific_break, when using gcc,
either C99 mode would need to be enabled, or the code would need to
change. I changed a couple loop variable definitions to conform
to pre-C99 to simplify testing the fix. The second issue was
the necessity to include -lpthread as a linker option in the Makefile.
Any issues with that part are due to me (Todd Fiala).
llvm-svn: 199426
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
we would return
control to the user anyway. This was put in to handle monitors that would say there was no
stop reason when you first attached to them. But it broke the case where you hit a thread specific
breakpoint on many threads, but NOT the one specified in the breakpoint. I work around this
by only doing the junky override when the StopID is 0 - i.e. on first attach.
This commit also adds a test for thread specific breakpoints.
llvm-svn: 199290
|
|
|
|
| |
llvm-svn: 198962
|
|
|
|
| |
llvm-svn: 198961
|
|
|
|
|
|
|
|
|
|
|
| |
The "type format add" command gets a new flag --type (-t). If you pass -t <sometype>, upon fetching the value for an object of your type,
LLDB will display it as-if it was of enumeration type <sometype>
This is useful in cases of non-contiguous enums where there are empty gaps of unspecified values, and as such one cannot type their variables as the enum type,
but users would still like to see them as-if they were of the enum type (e.g. DWARF field types with their user-reserved ranges)
The SB API has also been improved to handle both types of formats, and a test case is added
llvm-svn: 198105
|
|
|
|
|
|
| |
llvm.org/pr18313
llvm-svn: 197910
|
|
|
|
|
|
| |
and remote targets.
llvm-svn: 197266
|
|
|
|
|
|
|
|
|
|
| |
test_convenience_registers_16bit_with_process_attach fails due to
pr18200. The test has a @expectedFailureFreeBSD decorator, but it
appears this does not catch a RuntimError exception raised in the test
infrastructure, so the test still reports failure. For now just skip
it.
llvm-svn: 197174
|
|
|
|
|
|
|
|
|
|
| |
"mydir" inside each test case.
This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated.
Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you.
llvm-svn: 196985
|
|
|
|
| |
llvm-svn: 196941
|
|
|
|
|
|
| |
Also add decorator for an issue that this uncovered: llvm.org/pr18200
llvm-svn: 196920
|
|
|
|
| |
llvm-svn: 196919
|
|
|
|
|
|
|
| |
llvm.org/pr18190
llvm.org/pr18191
llvm-svn: 196792
|
|
|
|
|
|
|
| |
llvm.org/pr17944
llvm.org/pr17946
llvm-svn: 196786
|
|
|
|
|
|
| |
llvm.org/pr16706
llvm-svn: 196781
|
|
|
|
|
|
|
|
|
|
| |
@skipIfRemoteDueToDeadlock.
@skipIfRemote is used to decorate test cases that don't make sense to run remotely.
@skipIfRemoteDueToDeadlock indicates these tests need to be looked at and currently deadlock the running of the test suite when run on remote systems. These issues should be fixed soon.
llvm-svn: 196543
|
|
|
|
| |
llvm-svn: 196313
|
|
|
|
|
|
|
|
|
|
|
|
| |
A number of tests fail to build on FreeBSD because the test build script
defaults to libstdc++ for clang. On FreeBSD the libstdc++ is rather old
and libc++ should be used instead.
(These tests previously had an @expectedFailureFreeBSD decorator for
pr16696, the umbrella PR for the lack of threaded inferior support on
FreeBSD. The work to add that support will be committed soon.)
llvm-svn: 196101
|
|
|
|
|
|
|
|
|
|
| |
The test code locks mutexes from one thread and unlocks them from a
different one, which is not valid (it's either undefined behaviour or is
required to return an error).
See http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_mutex_lock.html
llvm-svn: 195707
|
|
|
|
|
|
|
| |
Watchpoints have not yet been implemented for FreeBSD.
llvm.org/pr16706
llvm-svn: 195649
|
|
|
|
|
|
|
|
| |
It fails on the buildbot, so skip for now to reduce the noise.
llvm.org/pr15037
llvm-svn: 195459
|
|
|
|
|
|
| |
This was a FreeBSD kernel issue, now fixed.
llvm-svn: 194842
|
|
|
|
|
|
|
| |
This failure was due to a limitation in the FreeBSD kernel that has now been
addressed. (llvm.org/pr17226 has the details.)
llvm-svn: 194731
|
|
|
|
|
|
|
| |
After solving the issue in llvm.org/pr17226 these two tests still fail,
now for other reasons.
llvm-svn: 194729
|
|
|
|
|
|
|
| |
After solving llvm.org/pr17226 these two tests now fail for the same reason
they do on Linux.
llvm-svn: 194726
|
|
|
|
|
|
|
|
| |
Fixed the test case for "test/functionalities/exec/TestExec.py" on Darwin.
The issue was breakpoints were persisting and causing problems. When we exec, we need to clear out the process and target and start fresh with nothing and let the breakpoints populate themselves again. This patch correctly clears out the breakpoints and also flushes the process so that the objects (process/thread/frame) give out valid information.
llvm-svn: 194106
|
|
|
|
|
|
| |
regardless of OS/hardware
llvm-svn: 193877
|
|
|
|
| |
llvm-svn: 193843
|
|
|
|
|
|
|
| |
Given that, this test will never pass
Marking as expected failure pending a fix
llvm-svn: 193830
|
|
|
|
| |
llvm-svn: 193829
|
|
|
|
|
|
|
|
| |
work
Mark it as expected to fail pending a fix
llvm-svn: 193828
|
|
|
|
| |
llvm-svn: 193827
|
|
|
|
| |
llvm-svn: 193826
|
|
|
|
| |
llvm-svn: 193825
|
|
|
|
| |
llvm-svn: 193824
|
|
|
|
| |
llvm-svn: 193822
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit reimplements the TypeImpl class (the class that backs SBType) in terms of a static,dynamic type pair
This is useful for those cases when the dynamic type of an ObjC variable can only be obtained in terms of an "hollow" type with no ivars
In that case, we could either go with the static type (+iVar information) or with the dynamic type (+inheritance chain)
With the new TypeImpl implementation, we try to combine these two sources of information in order to extract as much information as possible
This should improve the functionality of tools that are using the SBType API to do extensive dynamic type inspection
llvm-svn: 193564
|
|
|
|
|
|
|
|
|
| |
Extend DummySyntheticProvider to actually use debug-info vended children as the source of information
Make Python synthetic children either be valid, or fallback to the dummy, like their C++ counterparts
This allows LLDB to actually stop bailing out upon encountering an invalid synthetic children provider front-end, and still displaying the non synthetized ivar info
llvm-svn: 192741
|
|
|
|
| |
llvm-svn: 192467
|
|
|
|
|
|
| |
Remove 32-bit POSIX register hack in ConvertBetweenRegisterKinds.
llvm-svn: 192306
|