Mercurial > vim
view src/proto/debugger.pro @ 32051:e8c60d35fce3 v9.0.1357
patch 9.0.1357: using null_object results in an internal error
Commit: https://github.com/vim/vim/commit/c4e1b86cb0d88fa5ec1141d3c600e026dcc1bc21
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Feb 26 18:58:23 2023 +0000
patch 9.0.1357: using null_object results in an internal error
Problem: Using null_object results in an internal error. (Ernie Rael)
Solution: Add instructions for pushing an object and class. (closes https://github.com/vim/vim/issues/12044)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 26 Feb 2023 20:00:03 +0100 |
parents | 154663508d9b |
children | bede81965821 |
line wrap: on
line source
/* debugger.c */ int has_watchexpr(void); void do_debug(char_u *cmd); void ex_debug(exarg_T *eap); void dbg_check_breakpoint(exarg_T *eap); int dbg_check_skipped(exarg_T *eap); void ex_breakadd(exarg_T *eap); void ex_debuggreedy(exarg_T *eap); int debug_has_expr_breakpoint(void); void ex_breakdel(exarg_T *eap); void ex_breaklist(exarg_T *eap); linenr_T dbg_find_breakpoint(int file, char_u *fname, linenr_T after); int has_profiling(int file, char_u *fname, int *fp); void dbg_breakpoint(char_u *name, linenr_T lnum); /* vim: set ft=c : */