| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problems: Argument with 'nonnull' attribute passed null @ 277.
http://neovim.org/doc/reports/clang/report-9c3614.html#EndPath
Result of operation is garbage or undefined @ 281.
http://neovim.org/doc/reports/clang/report-45efbf.html#EndPath
Argument with 'nonnull' attribute passed null @ 306.
http://neovim.org/doc/reports/clang/report-ffb84f.html#EndPath
Result of operation is garbage or undefined @ 311.
http://neovim.org/doc/reports/clang/report-d04333.html#EndPath
Argument with 'nonnull' attribute passed null @ 315.
http://neovim.org/doc/reports/clang/report-786819.html#EndPath
Uninitialized argument value @ 328.
http://neovim.org/doc/reports/clang/report-2a5506.html#EndPath
Diagnostic: Multithreading issues.
Rationale : All reported problems can only occur if accesed globals
change state while executing function, which could only
happen in a multithreaded environment.
Resolution: Use local variables.
Note that this change alters function semantics, as now
function only depends on global values at entry time.
This shouldn't be a problem, though, as new semantics should
be in fact better.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem: Assigned value is garbage or undefined @ 187.
http://neovim.org/doc/reports/clang/report-7b7d61.html#EndPath.
Diagnostic: False positive.
Rationale : `colonp`, must be `>= modep, or null` by `vim_strchr`
postcondition. At this point we also it's not null and it's
not equal to `modep`, by previous code. So, it must be
`> modep`.
Resolution: Assert `colonp > modep`.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is currently possible for a client to send a response that doesn't match the
current server->client request(at the top of the stack). This commit fixes that
by delaying notifications to until the first `channel_send_call` invocation
returns.
Also remove the "call stack" size check, vim will already break if the call
stack goes too deep.
|
| | |
| |
| |
| | |
These valgrind entries are false positives because vim uses interior pointers.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The options_spec.lua suite has one purpose: Check if the :options commands will
throw any exception(:options is implemented by $VIMRUNTIME/optwin.vim). For this
it is best to use the `vim_command` API function since it will automatically
catch exceptions and forward them via msgpack-rpc.
Also, the option window seems to affect other tests, so call `restart` in the
teardown hook.
|
| |/
|
|
| |
This is required for testing scripts under the 'runtime' directory
|
| |\
| |
| | |
Restore TEST_FILE functionality for running individual tests.
|
| |/ |
|
| |\
| |
| | |
build: fix running of functional tests directly with CMake
|
| |/
|
|
|
|
|
| |
If you aren't just building everything into build/, then the functional
tests fail because they can't find the nvim executable. Let's pass in
the location of the nvim executable, and set NVIM_PRG environment
variable accordingly.
|
| |\
| |
| | |
Fix build warnings.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Remove build warning:
The target name "test" is reserved or not valid for certain CMake
features, such as generator expressions, and may result in undefined
behavior.
|
| | |
| |
| |
| |
| |
| | |
Remove build warning for Debug builds:
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)
|
| |/ |
|
| |\
| |
| | |
build: turn down the _FORTIFY_SOURCE level on gcc >= 4.0
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
| |
- Clean vim registers and functions before each test
- Add eval workaround to the request helper method
- Export dedent method
|
| |\ |
|
| |/ |
|
| |\ |
|
| |/
|
|
| |
- updated script_host_execute and script_host_execute_file to pass current range
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
A memory leak happens in uv_spawn when stdio is set to UV_IGNORE and the child
process fails to start. This only happens when libuv is compiled with gcc and
optimizations enabled(the default).
Compiling with '-O0' removes the leak, but all that can be done right now is
ignore the leak by adding a valgrind suppression.
|
| | |
| |
| |
| |
| | |
Travis build will now fail when core files are dumped, so call `abort()` when
the event loop is not fully released before exiting.
|
