Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 137 by zulolox4...@gmail.com: Memory fault-coredump unix aix
http://code.google.com/p/vim/issues/detail?id=137
What steps will reproduce the problem?
1.Edit a text file with 25000 lignes, about 3200 chars length every line
2.Split the lines to have 1600 chars length every, using a command like:
%s/word1, word2/word1,\r word2/
where word1 and word2 exists on every line at the middle (about).
3.After, I had a Memory fault(coredump), the message :
Vim: Caught deadly signal SEGV
Vim: Finished.
Memory fault(coredump)
What is the expected output?
The lines of text file have 1600 chars length.
What do you see instead?
Vim: Caught deadly signal SEGV
Vim: Finished.
Memory fault(coredump)
What version of the product are you using?
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Dec 11 2012 16:21:02)
Included patches: 1-754
Compiled by l1234u
Normal version without GUI. Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
-conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con +diff
+digraphs
-dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path
+find_in_path +float +folding -footer +fork() -gettext -hangul_input -iconv
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
-mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sgr
-mouse_sysmouse
-mouse_urxvt +mouse_xterm -multi_byte +multi_lang -mzscheme +netbeans_intg
+path_extra -perl +persistent_undo +postscript +printer -profile -python
-python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects
+title
-toolbar +user_commands +vertsplit +virtualedit +visual +visualextra
+viminfo
+vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset -xim
+xsmp_interact +xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g
Linking:
cc -qlanglvl=extc89 -o vim -lSM -lICE -lXt -lX11 -lm -lcurses
On what operating system?
Aix 6.1
Please provide any additional information below.
Using the debugging tool on Aix 6.1, dbx , vim binary and core dump the
stack at the crash was:
[using memory image in core]
reading symbolic information ...
Segmentation fault in may_core_dump at line 3166 in file "os_unix.c"
3166 kill(getpid(), deadly_signal); /* Die using the signal we
caught */
(dbx) where
may_core_dump(), line 3166 in "os_unix.c"
mch_exit(r = 1), line 3132 in "os_unix.c"
getout(exitval = 1), line 1478 in "main.c"
libdebug assertion "(framep->getGpr(STKP, &addr) == DB_SUCCESS &&
*nextStkpp == addr)" failed at line 1299 in
file ../../../../../../../../../../../src/bos/usr/ccs/lib/libdbx/libdebug/modules/stackdebug/POWER/stackdb_FrameProgress.C
preserve_exit(), line 9134 in "misc1.c"
deathtrap(sigarg = 11), line 1097 in "os_unix.c"
(dbx)
Best regards !
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
