|
Revision tags: llvmorg-3.6.0-rc2 |
|
| #
5275aaa0 |
| 15-Jan-2015 |
Vince Harron <[email protected]> |
Moved Args::StringToXIntYZ to StringConvert::ToXIntYZ
The refactor was motivated by some comments that Greg made http://reviews.llvm.org/D6918
and also to break a dependency cascade that caused fun
Moved Args::StringToXIntYZ to StringConvert::ToXIntYZ
The refactor was motivated by some comments that Greg made http://reviews.llvm.org/D6918
and also to break a dependency cascade that caused functions linking in string->int conversion functions to pull in most of lldb
llvm-svn: 226199
show more ...
|
|
Revision tags: llvmorg-3.6.0-rc1, llvmorg-3.5.1, llvmorg-3.5.1-rc2 |
|
| #
f2ef94e7 |
| 13-Dec-2014 |
Stephane Sezer <[email protected]> |
Make the platform process connect path less chatty.
Summary: If a stream contains an empty string, no need to append it to the output (otherwise we end up with a blank line). Also, no need to print
Make the platform process connect path less chatty.
Summary: If a stream contains an empty string, no need to append it to the output (otherwise we end up with a blank line). Also, no need to print a status message when the state changes to connected, as this string brings no information -- "Process 0" does not mean anything to the user, and the process being connected has no meaning either.
Test Plan: Connect to a remote linux platform mode daemon with `platform select remote-linux` followed by `platform connect ...`, create a target and run it, observe the output. Also, run the full test suite (dosep.py).
Before: (lldb) [...] connect, etc. (lldb) r Process 0 connected
Process 5635 launched: '/Users/sas/Source/test' (x86_64) Process 5635 stopped
After: (lldb) [...] connect, etc. (lldb) r Process 5635 launched: '/Users/sas/Source/test' (x86_64) Process 5635 stopped
Reviewers: tfiala, vharron, clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D6593
llvm-svn: 224188
show more ...
|
|
Revision tags: llvmorg-3.5.1-rc1 |
|
| #
8012cadb |
| 17-Nov-2014 |
Greg Clayton <[email protected]> |
Fixed more fallout from running the test suite remotely on iOS devices.
Fixed include: - Change Platform::ResolveExecutable(...) to take a ModuleSpec instead of a FileSpec + ArchSpec to help resolve
Fixed more fallout from running the test suite remotely on iOS devices.
Fixed include: - Change Platform::ResolveExecutable(...) to take a ModuleSpec instead of a FileSpec + ArchSpec to help resolve executables correctly when we have just a path + UUID (no arch). - Add the ability to set the listener in SBLaunchInfo and SBAttachInfo in case you don't want to use the debugger as the default listener. - Modified all places that use the SBLaunchInfo/SBAttachInfo and the internal ProcessLaunchInfo/ProcessAttachInfo to not take a listener as a parameter since it is in the launch/attach info now - Load a module's sections by default when removing a module from a target. Since we create JIT modules for expressions and helper functions, we could end up with stale data in the section load list if a module was removed from the target as the section load list would still have entries for the unloaded module. Target now has the following functions to help unload all sections a single or multiple modules:
size_t Target::UnloadModuleSections (const ModuleList &module_list);
size_t Target::UnloadModuleSections (const lldb::ModuleSP &module_sp);
llvm-svn: 222167
show more ...
|
| #
dc6224e0 |
| 21-Oct-2014 |
Greg Clayton <[email protected]> |
Make the "synchronous" mode actually work without race conditions.
There were many issues with synchronous mode that we discovered when started to try and add a "batch" mode. There was a race condit
Make the "synchronous" mode actually work without race conditions.
There were many issues with synchronous mode that we discovered when started to try and add a "batch" mode. There was a race condition where the event handling thread might consume events when in sync mode and other times the Process::WaitForProcessToStop() would consume them. This also led to places where the Process IO handler might or might not get popped when it needed to be.
llvm-svn: 220254
show more ...
|
|
Revision tags: llvmorg-3.5.0, llvmorg-3.5.0-rc4, llvmorg-3.5.0-rc3 |
|
| #
5163792b |
| 19-Aug-2014 |
Todd Fiala <[email protected]> |
Adjust process launch --disable-aslr to take true/false value.
This change modifies the 'process launch' --disable-aslr option to take a boolean argument. If the user directly specifies --disable-a
Adjust process launch --disable-aslr to take true/false value.
This change modifies the 'process launch' --disable-aslr option to take a boolean argument. If the user directly specifies --disable-aslr {true,false}, that setting will control whether the process is launched with ASLR disabled accordingly. In the event that the setting is not explicitly made on the process launch command line, then the value is retrieved from the target.disable-aslr setting (i.e. settings show target.disable-aslr).
llvm-svn: 215996
show more ...
|
| #
a3b89e27 |
| 12-Aug-2014 |
Todd Fiala <[email protected]> |
Fix iohandler prompt race condition.
This issue caused the lldb prompt to not show up in certain cases, very noticeable on Linux systems.
See details on this review: http://reviews.llvm.org/D4863
Fix iohandler prompt race condition.
This issue caused the lldb prompt to not show up in certain cases, very noticeable on Linux systems.
See details on this review: http://reviews.llvm.org/D4863
And on this lldb-commits thread: http://lists.cs.uiuc.edu/pipermail/lldb-commits/Week-of-Mon-20140811/012306.html
Change by Shawn Best.
(Much useful help and testing by the rest of the community, thanks all!)
llvm-svn: 215446
show more ...
|
|
Revision tags: llvmorg-3.5.0-rc2 |
|
| #
06357c93 |
| 30-Jul-2014 |
Greg Clayton <[email protected]> |
(no commit message)
llvm-svn: 214319
|
|
Revision tags: llvmorg-3.5.0-rc1 |
|
| #
d37221dc |
| 09-Jul-2014 |
Zachary Turner <[email protected]> |
Revert "Fix broken tests due to new error output."
This reverts commit ec7c94f8e6860968d384b578e5564a9c55c80b4a and re-enables OptionValidators.
llvm-svn: 212627
|
| #
9734280f |
| 08-Jul-2014 |
Todd Fiala <[email protected]> |
Fix broken tests due to new error output.
This reverses out the options validators changes. We'll get these back in once the changes to the output can be resolved.
Restores broken tests on FreeBSD
Fix broken tests due to new error output.
This reverses out the options validators changes. We'll get these back in once the changes to the output can be resolved.
Restores broken tests on FreeBSD, Linux, MacOSX.
Changes reverted: r212500, r212317, r212290.
llvm-svn: 212543
show more ...
|
| #
de963e9a |
| 03-Jul-2014 |
Zachary Turner <[email protected]> |
Adds the notion of an OptionValidator.
The purpose of the OptionValidator is to determine, based on some arbitrary set of conditions, whether or not a command option is valid for a given debugger st
Adds the notion of an OptionValidator.
The purpose of the OptionValidator is to determine, based on some arbitrary set of conditions, whether or not a command option is valid for a given debugger state. An example of this might be to selectively disable or enable certain command options that don't apply to a particular platform.
This patch contains no functional change, and does not actually make use of an OptionValidator for any purpose yet. A follow-up patch will begin to add the logic and users of OptionValidator.
Reviewed by: Greg Clayton, Jim Ingham
Differential Revision: http://reviews.llvm.org/D4369
llvm-svn: 212290
show more ...
|
| #
106d0286 |
| 25-Jun-2014 |
Jim Ingham <[email protected]> |
Added an option to turn OFF the "detach on error" behavior that was added to debugserver when launching processes.
<rdar://problem/16216199>
llvm-svn: 211658
|
| #
a2715cf1 |
| 13-Jun-2014 |
Greg Clayton <[email protected]> |
Added the ability to save core files:
(lldb) file /bin/ls (lldb) b malloc (lldb) run (lldb) process save-core /tmp/ls.core
Each ObjectFile plug-in now has the option to save core files by registeri
Added the ability to save core files:
(lldb) file /bin/ls (lldb) b malloc (lldb) run (lldb) process save-core /tmp/ls.core
Each ObjectFile plug-in now has the option to save core files by registering a new static callback.
llvm-svn: 210864
show more ...
|
|
Revision tags: llvmorg-3.4.2, llvmorg-3.4.2-rc1, llvmorg-3.4.1, llvmorg-3.4.1-rc2, llvmorg-3.4.1-rc1 |
|
| #
6c9ed91c |
| 03-Apr-2014 |
Jim Ingham <[email protected]> |
Make the fail messages
llvm-svn: 205497
|
| #
e556a423 |
| 03-Mar-2014 |
Greg Clayton <[email protected]> |
Stop messages from being emitted out of order when detaching.
llvm-svn: 202756
|
| #
44d93782 |
| 27-Jan-2014 |
Greg Clayton <[email protected]> |
Merging the iohandler branch back into main.
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 embe
Merging the iohandler branch back into main.
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
show more ...
|
|
Revision tags: llvmorg-3.4.0, llvmorg-3.4.0-rc3 |
|
| #
b09c5384 |
| 13-Dec-2013 |
Greg Clayton <[email protected]> |
Centralized the launching of a process into Target::Launch()
While investigating test suite failures when running the test suite remotely, I noticed we had 3 copies of code that launched a process:
Centralized the launching of a process into Target::Launch()
While investigating test suite failures when running the test suite remotely, I noticed we had 3 copies of code that launched a process: 1 - in "process launch" command 2 - SBTarget::Launch() with args 3 - SBTarget::Launch() with SBLaunchInfo
"process launch" was launching through the platform if it was supported (this is needed for remote debugging) and the 2 and 3 were not.
Now all code is in one place.
llvm-svn: 197247
show more ...
|
|
Revision tags: llvmorg-3.4.0-rc2 |
|
| #
8c8018d3 |
| 22-Nov-2013 |
Greg Clayton <[email protected]> |
Only use a PTY master/slave when launching for local processes.
llvm-svn: 195483
|
|
Revision tags: llvmorg-3.4.0-rc1 |
|
| #
9e9919f0 |
| 09-Oct-2013 |
Daniel Malea <[email protected]> |
Allow Process::WaitForProcessToStop to return immediately if process is already in the stopped state - By default, the above function will wait for at least one event - Set wait_always=false to make
Allow Process::WaitForProcessToStop to return immediately if process is already in the stopped state - By default, the above function will wait for at least one event - Set wait_always=false to make the function return immediately if the process is already stopped
llvm-svn: 192301
show more ...
|
| #
e2607b50 |
| 05-Sep-2013 |
Virgile Bello <[email protected]> |
Add OptionParser.h
llvm-svn: 190063
|
|
Revision tags: llvmorg-3.3.1-rc1, llvmorg-3.3.0, llvmorg-3.3.0-rc3, llvmorg-3.3.0-rc2 |
|
| #
f9b57b9d |
| 10-May-2013 |
Greg Clayton <[email protected]> |
<rdar://problem/13700260>
Avoid a deadlock when using the OperatingSystemPython code and typing "process interrupt". There was a possible lock inversion between the target API lock and the process'
<rdar://problem/13700260>
Avoid a deadlock when using the OperatingSystemPython code and typing "process interrupt". There was a possible lock inversion between the target API lock and the process' thread list lock due to code trying to discard the thread list. This was fixed by adding a boolean to Process::Halt() that indicates if the thread plans should be discarded and doing it in the private state thread when we process the stopped state.
llvm-svn: 181651
show more ...
|
|
Revision tags: llvmorg-3.3.0-rc1 |
|
| #
acff8950 |
| 02-May-2013 |
Jim Ingham <[email protected]> |
Recommitting r180831 with trivial fix - remember to return errors if you compute.
llvm-svn: 180898
|
| #
54e39db8 |
| 01-May-2013 |
Daniel Malea <[email protected]> |
Reverting 180831 as it crashes TestDefaultConstructorForAPIObjects.py
llvm-svn: 180868
|
| #
a23f73db |
| 30-Apr-2013 |
Jim Ingham <[email protected]> |
Added an option to "process detach" to keep the process stopped, if the process plugin (or in the case of ProcessGDBRemote the stub we are talking to) know how to do that.
rdar://problem/13680832
l
Added an option to "process detach" to keep the process stopped, if the process plugin (or in the case of ProcessGDBRemote the stub we are talking to) know how to do that.
rdar://problem/13680832
llvm-svn: 180831
show more ...
|
| #
dcb1d856 |
| 29-Mar-2013 |
Jim Ingham <[email protected]> |
“process launch” should “detach” not “kill” if the current process was one we attached to. “process attach” should ask the same questions as process launch if there is a current process. “process con
“process launch” should “detach” not “kill” if the current process was one we attached to. “process attach” should ask the same questions as process launch if there is a current process. “process connect” then “process launch” or “process attach” should actually work.
<rdar://problem/13524210> <rdar://problem/13524208> <rdar://problem/13488919>
llvm-svn: 178324
show more ...
|
| #
0161b49c |
| 09-Feb-2013 |
Jim Ingham <[email protected]> |
Reworked the way Process::RunThreadPlan and the ThreadPlanCallFunction interoperate to fix problems where hitting auto-continue signals while running a thread plan would cause us to lose control of t
Reworked the way Process::RunThreadPlan and the ThreadPlanCallFunction interoperate to fix problems where hitting auto-continue signals while running a thread plan would cause us to lose control of the debug session.
<rdar://problem/12993641>
llvm-svn: 174793
show more ...
|