| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 283929
|
|
|
|
|
|
| |
on i386.
llvm-svn: 283923
|
|
|
|
|
|
| |
Add an executable that we can debug.
llvm-svn: 283835
|
|
|
|
| |
llvm-svn: 283821
|
|
|
|
| |
llvm-svn: 283820
|
|
|
|
| |
llvm-svn: 283813
|
|
|
|
|
| |
Subscribers: jaydeep, bhushan, slthakur, llvm-commits
llvm-svn: 283739
|
|
|
|
|
|
|
|
|
|
|
|
| |
loop
Reviewers: clayborg, labath
Subscribers: jaydeep, bhushan, slthakur, llvm-commits
Differential Revision: https://reviews.llvm.org/D24549
llvm-svn: 283732
|
|
|
|
|
|
|
| |
Tracked by:
rdar://28658860
llvm-svn: 283493
|
|
|
|
|
|
|
| |
Tracked by:
rdar://28656605
llvm-svn: 283483
|
|
|
|
|
|
|
| |
Tracked by:
rdar://28656532
llvm-svn: 283482
|
|
|
|
|
|
|
| |
Tracked by:
rdar://28656408
llvm-svn: 283481
|
|
|
|
|
|
|
| |
Tracked by:
rdar://28655626
llvm-svn: 283477
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(Intel(R) MPX)
Summary:
This patch adds support for handling the SIGSEGV signal with 'si_code ==
SEGV_BNDERR', which is thrown when a bound violation is caught by the
Intel(R) MPX technology.
Differential Revision: https://reviews.llvm.org/D25329
llvm-svn: 283474
|
|
|
|
| |
llvm-svn: 283468
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Let the inferior test code determine if CPU and kernel support Intel(R)
MPX and cleanup test script.
Differential Revision: https://reviews.llvm.org/D25328
llvm-svn: 283461
|
|
|
|
|
|
| |
Xfails added and/or removed to reflect the current state of Windows.
llvm-svn: 283380
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tests are failing and build is failing on windows and darwin.
Will fix and commit it later
-------------------------------------------------------------
Revert "xfailing minidump tests again ... :("
This reverts commit 97eade002c9e43c1e0d11475a4888083a8965044.
Revert "Fixing new Minidump plugin tests"
This reverts commit 0dd93b3ab39c8288696001dd50b9a093b813b09c.
Revert "Add the new minidump files to the Xcode project."
This reverts commit 2f638a1d046b8a88e61e212220edc40aecd2ce44.
Revert "xfailing tests for Minidump plugin"
This reverts commit 99311c0b22338a83e6a00c4fbddfd3577914c003.
Revert "Adding a new Minidump post-mortem debugging plugin"
This reverts commit b09a7e4dae231663095a84dac4be3da00b03a021.
llvm-svn: 283352
|
|
|
|
| |
llvm-svn: 283324
|
|
|
|
| |
llvm-svn: 283321
|
|
|
|
|
|
|
|
| |
the tests are failing on the buildbot because there is an extra frame
(maybe) on the call stack.
Will investigate tomorrow.
llvm-svn: 283263
|
|
|
|
| |
llvm-svn: 283262
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This plugin resembles the already existing Windows-only Minidump plugin.
The WinMinidumpPlugin uses the Windows API for parsing Minidumps
while this plugin is cross-platform because it includes a Minidump
parser (which is already commited)
It is able to produce a backtrace, to read the general puprose regiters,
inspect local variables, show image list, do memory reads, etc.
For now the only arch that this supports is x86 64 bit
This is because I have only written a register context for that arch.
Others will come in next CLs.
I copied the WinMinidump tests and adapted them a little bit for them to
work with the new plugin (and they pass)
I will add more tests, aiming for better code coverage.
There is still functionality to be added, see TODOs in code.
Reviewers: labath, zturner
Subscribers: beanz, mgorny, amccarth, lldb-commits, modocache
Differential Revision: https://reviews.llvm.org/D25196
llvm-svn: 283259
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Use os.getcwd() instead of get_process_working_directory() as prefix for
souce file.
Reviewers: labath
Subscribers: lldb-commits
Differential Revision: https://reviews.llvm.org/D25217
llvm-svn: 283171
|
|
|
|
|
|
|
| |
Since we count on it in a few places, the test verifies that the
test instance has an id() method that returns something non-None.
llvm-svn: 283156
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The lldbutil.run_break_set_by_file_and_line has already checked that the number of
locations was 1, so don't check it again. And certainly don't check it again by
grubbing in break list output.
Also, we know the Thread's IsStopped state is wrong, and have a test for that, so
don't keep testing it in other files where that isn't the primary thing we're testing.
I removed the xfail for Darwin. If this also passes on other systems, we can remove
the xfails from them as we find that out.
llvm-svn: 282993
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the test for thread stopped states from this test.
That isn't set properly now, and its setting doesn't matter till we actually support non-stop debugging, so
we shouldn't have unrelated tests failing from it.
Also changed some code that was trying and failing to grub command line output, and replaced
it by SB API calls.
llvm-svn: 282976
|
|
|
|
| |
llvm-svn: 282970
|
|
|
|
| |
llvm-svn: 282969
|
|
|
|
| |
llvm-svn: 282966
|
|
|
|
| |
llvm-svn: 282830
|
|
|
|
| |
llvm-svn: 282824
|
|
|
|
|
|
| |
call, for that is not true in i386 mode
llvm-svn: 282823
|
|
|
|
|
|
|
|
| |
types from the ObjC runtime
"Fixes" rdar://28501616
llvm-svn: 282774
|
|
|
|
|
|
|
|
| |
std::map::iterator, rendering LLDB unable to display elements vended by an iterator
Fixes <rdar://problem/28237521>
llvm-svn: 282648
|
|
|
|
|
|
| |
<rdar://problem/28476369>
llvm-svn: 282632
|
|
|
|
|
|
|
|
|
|
| |
We only use the .o-style debug info here regardless, so having
it run all three debuginfo styles was a waste.
This also strips out the custom build function and uses the
TestBase.build() method.
llvm-svn: 282508
|
|
|
|
|
|
|
| |
Tracked by:
rdar://28476369
llvm-svn: 282496
|
|
|
|
|
|
|
|
|
|
|
| |
CommandData breakpoint commands didn't know whether they were
Python or Command line commands, so they couldn't serialize &
deserialize themselves properly. Fix that.
I also changed the "breakpoint list" command to note in the output
when the commands are Python commands. Fortunately only one test
was relying on this explicit bit of text output.
llvm-svn: 282432
|
|
|
|
|
|
|
| |
Nobody is running the test suite with icc, so we have no idea if they pass. But
the bug they link to has definitely been fixed.
llvm-svn: 282408
|
|
|
|
| |
llvm-svn: 282212
|
|
|
|
|
|
| |
Also tests for this and the ThreadSpec serialization.
llvm-svn: 282207
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change introduces optional marking of the column within a source
line where a thread is stopped. This marking will show up when the
source code for a thread stop is displayed, when the debug info
knows the column information, and if the optional column marking is
enabled.
There are two separate methods for handling the marking of the stop
column:
* via ANSI terminal codes, which are added inline to the source line
display. The default ANSI mark-up is to underline the column.
* via a pure text-based caret that is added in the appropriate column
in a newly-inserted blank line underneath the source line in
question.
There are some new options that control how this all works.
* settings set stop-show-column
This takes one of 4 values:
* ansi-or-caret: use the ANSI terminal code mechanism if LLDB
is running with color enabled; if not, use the caret-based,
pure text method (see the "caret" mode below).
* ansi: only use the ANSI terminal code mechanism to highlight
the stop line. If LLDB is running with color disabled, no
stop column marking will occur.
* caret: only use the pure text caret method, which introduces
a newly-inserted line underneath the current line, where
the only character in the new line is a caret that highlights
the stop column in question.
* none: no stop column marking will be attempted.
* settings set stop-show-column-ansi-prefix
This is a text format that indicates the ANSI formatting
code to insert into the stream immediately preceding the
column where the stop column character will be marked up.
It defaults to ${ansi.underline}; however, it can contain
any valid LLDB format codes, e.g.
${ansi.fg.red}${ansi.bold}${ansi.underline}
* settings set stop-show-column-ansi-suffix
This is the text format that specifies the ANSI terminal
codes to end the markup that was started with the prefix
described above. It defaults to: ${ansi.normal}. This
should be sufficient for the common cases.
Significant leg-work was done by Adrian Prantl. (Thanks, Adrian!)
differential review: https://reviews.llvm.org/D20835
reviewers: clayborg, jingham
llvm-svn: 282105
|
|
|
|
| |
llvm-svn: 282103
|
|
|
|
|
|
|
|
|
|
| |
Serialize breakpoint names & the hardware_requested attributes.
Also added a few missing affordances to SBBreakpoint whose absence
writing the tests pointed out.
<rdar://problem/12611863>
llvm-svn: 282036
|
|
|
|
|
|
| |
Plus a few bug fixes I found along the way.
llvm-svn: 281690
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It looks like the message-content-retrieval aspect of DarwinLog
support is flaky, not just the regex match against it. Slightly
less frequently than the regex matching, I am seeing the
direct string-match variant of log-message-content matching
also fail.
Tracked by:
llvm.org/pr30299
rdar://28237450
llvm-svn: 281251
|
|
|
|
|
|
|
|
|
|
| |
These tests are not working reliably. I'm marking them
xfail until I resolve the issue.
Tracked by:
llvm.org/pr30299
llvm-svn: 281058
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: clayborg, labath
Subscribers: jaydeep, bhushan, slthakur, lldb-commits
Differential Revision: https://reviews.llvm.org/D24122
llvm-svn: 281031
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: Signed-off-by: Valentina Giusti <valentina.giusti@intel.com>
Reviewers: dvlahovski, granata.enrico, clayborg, labath
Subscribers: lldb-commits
Differential Revision: https://reviews.llvm.org/D24255
llvm-svn: 280942
|