Cesar Romani wrote:
Dominique Pellé wrote:
...
When putting a breakpoint at line term.c:1615,
what is the value of 'term' variable? (output of gdb command: print term)
Ex:
(gdb) p term
$1 = (char_u *) 0x946e25c xterm-256color
$1 = (char_u *) 0xa0158c0 msys
What is also the value of
Dominique Pellé wrote:
Cesar Romani wrote:
Dominique Pellé wrote:
...
When putting a breakpoint at line term.c:1615,
what is the value of 'term' variable? (output of gdb command: print
term)
Ex:
(gdb) p term
$1 = (char_u *) 0x946e25c xterm-256color
$1 = (char_u *) 0xa0158c0 msys
Dominique Pellé wrote:
Cesar Romani wrote:
Dominique Pellé wrote:
...
When putting a breakpoint at line term.c:1615,
what is the value of 'term' variable? (output of gdb command: print
term)
Ex:
(gdb) p term
$1 = (char_u *) 0x946e25c xterm-256color
$1 = (char_u *)
Cesar Romani wrote:
Dominique Pellé wrote:
...
When putting a breakpoint at line term.c:1615,
what is the value of 'term' variable? (output of gdb command: print
term)
Ex:
(gdb) p term
$1 = (char_u *) 0x946e25c xterm-256color
$1 = (char_u *) 0xa0158c0 msys
What is also
Cesar Romani wrote:
1675 if ((error_msg = tgetent_error(tbuf, term)) == NULL)
(gdb) p term
$11 = (char_u *) 0xa0158c0 msys
(gdb) n
1677 tp = tstrbuf;
(gdb) p term
$12 = (char_u *) 0x5b455c3d Address 0x5b455c3d out of bounds
1/ OK, so the corruption
Dominique Pellé wrote:
Cesar Romani wrote:
1675if ((error_msg = tgetent_error(tbuf, term)) == NULL)
(gdb) p term
$11 = (char_u *) 0xa0158c0 msys
(gdb) n
1677tp = tstrbuf;
(gdb) p term
$12 = (char_u *) 0x5b455c3d Address 0x5b455c3d out of bounds
1/
Cesar Romani wrote:
Dominique Pellé wrote:
I suspect that on your system (mingw), it's using 1024 instead
of 2048. If so, the attached patch might fix it. It adds
defined(__MINGW32__) (__MINGW32__ is already used
in several places in Vim's code):
1348 #if defined(AMIGA) ||
Breakpoint 1, set_termname (term=0xa0158c0 msys) at term.c:1615
1615if (term_is_builtin(term))
(gdb) p term
$1 = (char_u *) 0xa0158c0 msys
(gdb) n
1634for (try = builtin_first ? 0 : 1; try 3; ++try)
(gdb) p term
$2 = (char_u *) 0xa0158c0 msys
(gdb) n
1639if
Dominique Pellé wrote:
Cesar Romani wrote:
Dominique Pellé wrote:
I suspect that on your system (mingw), it's using 1024 instead
of 2048. If so, the attached patch might fix it. It adds
defined(__MINGW32__) (__MINGW32__ is already used
in several places in Vim's code):
1348 #if
On Sun, Jun 7, 2009 at 10:07 PM, Cesar Romani wrote:
Thanks a lot for your help.
Actually when I press backspace, it behaves like the cursor left and
when I press escape the characters left behind are deleted.
CTRL-h cannot delete either, neither :fixdel can fix the backspace.
But When I
Cesar Romani wrote:
I tried compiling vim 7.2 with termcap on MSYS, and it compiles fine.
However, when I execute it, I get:
$ vim
Vim: Caught deadly signal SEGV
Vim: Finished.
If I run gdb on it, I get:
$ gdb vim.exe
Bram Moolenaar wrote:
Cesar Romani wrote:
I tried compiling vim 7.2 with termcap on MSYS, and it compiles fine.
However, when I execute it, I get:
$ vim
Vim: Caught deadly signal SEGV
Vim: Finished.
If I run gdb on it, I get:
Cesar Romani wrote:
Bram Moolenaar wrote:
Cesar Romani wrote:
I tried compiling vim 7.2 with termcap on MSYS, and it compiles fine.
However, when I execute it, I get:
$ vim
Vim: Caught deadly signal SEGV
Vim: Finished.
If I run gdb on it, I
Dominique Pellé wrote:
Cesar Romani wrote:
Bram Moolenaar wrote:
Cesar Romani wrote:
I tried compiling vim 7.2 with termcap on MSYS, and it compiles fine.
However, when I execute it, I get:
$ vim
Vim: Caught deadly signal SEGV
Vim: Finished.
I tried compiling vim 7.2 with termcap on MSYS, and it compiles fine.
However, when I execute it, I get:
$ vim
Vim: Caught deadly signal SEGV
Vim: Finished.
If I run gdb on it, I get:
$ gdb vim.exe
GNU gdb 6.8
Copyright (C) 2008 Free
15 matches
Mail list logo
