vim/vim-vebugger
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
139 Commits 1 Branch 8 Tags
Commit Graph

93 Commits

Author SHA1 Message Date
wsdjeg
876af0d1c2 Use full command names 2017-12-18 22:40:40 +08:00
wsdjeg
9c47e1b243 Add options for set sign text 2017-12-18 22:18:09 +08:00
wsdjeg
cd61f1029c Add filetype 2017-12-13 21:23:28 +08:00
Idan Arye
f2b00c8c61 Merge pull request #45 from daltonmatos/feature/hightlight-current-debugged-line 
Highlight current executed line (bg=red fg=white)
 2017-10-17 21:51:57 +03:00
Dalton Barreto
5fedcab009
Highlight current debugged line with DebuggedLine 
If the `DebuggedLine` highlight-group exist, highlight the current
debugged line with it.
 2017-10-17 16:49:35 -02:00
Dalton Barreto
01326cc9be
Removing redundant variable l:one_path 2017-10-16 20:36:12 -02:00
Dalton Barreto
5865e3b28e
Adding support for srcpath as string or list 2017-10-16 20:11:15 -02:00
Dalton Barreto
4230773e7e
Add support for multi-srcpath 
Now Vebugger can search for a sourcecode in multiple srcpath locations.
The first match is returned and it's the file Vebugger will show.
 2017-10-16 12:06:08 -02:00
Ingo Heimbach
a2e2dcd612 Use feedkeys for echoing evaluated expressions 
Echo commands in vim 8 timer handlers do not wait for the user to
confirm. Echoing via feedkeys circumvents this problem.
 2017-01-22 12:39:06 +01:00
Ingo Heimbach
e684fdffd9 Use vim 8 timers for continuous checking of debugger output 2017-01-08 11:07:48 +01:00
Ingo Heimbach
d78fa68a72 Improved locating the currently debugged program position 
(the old algorithm had problems with double frees for example)
 2016-11-05 18:37:06 +01:00
Ingo Heimbach
c7304dc1f1 LLDB only uses the python interpreter stored in 
"g:vebugger_path_python_lldb"
Updated the documentation to explain why a special python variable is
needed for LLDB
 2016-11-05 18:37:06 +01:00
Ingo Heimbach
5187166c44 ~/.lldbinit is executed 2016-11-05 18:37:06 +01:00
Ingo Heimbach
cd82aea820 Added macOS compatibility for the lldb extension 2016-11-05 18:37:06 +01:00
Ingo Heimbach
8897e79b75 Added the lldb debugger via the lldb python api 2016-11-05 18:37:06 +01:00
Ingo Heimbach
c1913b3994 Bugfix: The PDB where function is not aware of step outs 2016-11-05 10:28:59 +01:00
IdanArye
78893b6e5f Fix #25 set print pretty off and print array off in GDB 2016-02-20 18:02:00 +02:00
IdanArye
3ef3f45016 Fix #25 - pre-process GDB's MI output 2016-02-17 00:44:19 +02:00
Idan Arye
fa84d5c0a5 Fix #24 - typo: Ternimal -> Terminal 2016-01-26 19:21:19 +02:00
IdanArye
fa63556530 Fix #23 - Remove usage of bufexists 
`bufexists` can't handle the home directory(`~`). Instead use `bufnr`
and `bufwinnr`, which are more appropriate.

Also, I've decided to use `bufwinnr` instead of `bufnr` for checking if
the file exists before loading it with `g:vebugger_view_source_cmd`, so
it'll use `g:vebugger_view_source_cmd` if no window displays the buffer
- even if the buffer is loaded. This fixes an inconsistency that was
before, that `g:vebugger_view_source_cmd` would get invoked only if the
file has no buffer loaded, if there is a buffer loaded it'll jump to it
from the current window.
 2015-11-06 22:30:02 +02:00
Alexey Balchunas
b9517ade8c Do not use tags for callstack, only for current location. Otherwise, it's unusably slow. 2015-09-06 10:53:44 +07:00
Alexey Balchunas
d6513dfb88 Fixed a critical bug in source searching using tags 2015-09-05 23:42:48 +07:00
Alexey Balchunas
30218447f8 added an option to enable usage of tags 2015-09-05 23:42:48 +07:00
Alexey Balchunas
a1027767d4 The simple class name was calculated with prefixed '.' character 2015-09-05 23:42:42 +07:00
Idan Arye
94b08ebc03 Merge pull request #21 from bleshik/feature/use-tags 
Use tags when searching for a source file for jdb
 2015-09-05 18:30:08 +03:00
Idan Arye
8289c7c1d2 Merge pull request #20 from bleshik/feature/support-for-groovy 
Support for Groovy
 2015-09-05 18:29:56 +03:00
Alexey Balchunas
281e7505c3 Use tags when searching for a source file for jdb 2015-09-05 22:15:14 +07:00
Alexey Balchunas
06ae5e977e Make package parsing work for groovy 2015-09-05 12:45:04 +07:00
David Nguyen
806d6228cc Close shell buffer when killing the debugger 2015-06-27 14:03:03 +02:00
IdanArye
acda6c5b12 Merge branch 'master' into develop 2015-05-29 16:18:45 +03:00
IdanArye
2f52caac25 Fix #17 - Vebugger interfieres with Ctrlp plugin 
Use `'n'` mode with `feedkeys("f\e")` to prevent CtrlP's mapping from
interpreting `f` as actual "add `f` and close the window"...
 2015-05-29 16:16:36 +03:00
IdanArye
fe8685ad84 Close #13 only use BreakPoint highlight only if it's predefined 2015-04-15 23:03:28 +03:00
IdanArye
df8e4ddbc9 Check that the BreakPoint highlight style doesn't exist before redfining it 2015-04-11 17:59:02 +03:00
Kevin Brandon
bc0c05713d Fixes issue #13 by defining a color group called BreakPoint. By default it reverses the color scheme for term, cterm, and gui 2015-04-11 02:10:03 -07:00
IdanArye
f98c830b82 Changed the Vebugger_*UserAction activation to use try...finally 
That way, errors in the event listeners will neither be swallowed nor
will they prevent the user action from happening.
 2015-03-01 21:32:20 +02:00
IdanArye
e3c069b5b6 Add hook for pre&post user actions 2015-02-28 19:45:05 +02:00
IdanArye
4567ad166b Change the code path of user actions 
Most user actions now go through vebugger#userAction, which calls the
user action on the active debugger object. The exceptions are:

 - Starting the debugger - because we don't have an active debugger yet
 - Stopping the debugger - because we'll need to clear the active
   debugger after that
 - Altering breakpoints - because we want to be able to do it even
   without an active debugger(e.g. - setting breakpoints before starting
   the debugger)
 2015-02-28 19:16:25 +02:00
Idan Arye
3f13848d67 Merge pull request #8 from rdnetto/feature/flexible-opening 
Added configuration option g:vebugger_edit_cmd
 2015-02-16 11:11:06 +02:00
Reuben D'Netto
2914f5a116 Added configuration option g:vebugger_edit_cmd 2015-02-16 16:29:29 +11:00
IdanArye
a97d06519a Add docs for the 'con' flag for gdb 
Also expand :VBGattachGDB to support either 'pid' or 'con' as second
command argument.
 2015-02-16 00:41:08 +02:00
Reuben D'Netto
940af913be "Added 'con' option to vebugger#gdb#start" 2015-02-15 16:45:00 +11:00
IdanArye
b8dd945557 Fix #5 - Vim7.3 compatibility 2015-01-24 02:12:49 +02:00
IdanArye
f93bac384b Fix indentation and bump bugfix version 2015-01-14 22:08:41 +02:00
IdanArye
31a8bd64c8 Fixed breakpoints for MDBG in Cygwin 
Now I just need to see that everything works in regular Vim under Windows...
 2015-01-14 00:53:36 +02:00
IdanArye
6d9ace9f62 Fix paths for MDbg in Cygwin 2015-01-13 00:22:02 +02:00
IdanArye
f51ff80896 Fix for line stops in GDB. 
Apperantly GDB changed the format, so Vebugger was changed to reflect
that.
 2014-08-30 00:40:21 +03:00
IdanArye
5036961da9 Add support for multiple versions of debuggers 2014-06-24 01:46:03 +03:00
IdanArye
b0be0c92b7 Allow GDB to work with Dlang executables 
This is done by allowing to choose differet entry points to start the
program at.
 2014-06-24 00:07:28 +03:00
IdanArye
f0368a1de6 Use a pattern instead of fnamemodify for MDbg breakpoints 2014-06-12 20:48:38 +03:00
unknown
854f86d067 Added more supported characters to method full name in MDBG where parsing 2014-06-10 11:45:24 +03:00