Loading ...
Sorry, an error occurred while loading the content.

71434Re: Issue 137 in vim: Memory fault-coredump unix aix

Expand Messages
  • Zulox4
    Jun 21, 2013
    • 0 Attachment
      On Saturday, June 22, 2013 6:32:56 AM UTC+2, v...@... wrote:
      > Comment #1 on issue 137 by dominiqu...@...: Memory fault-coredump
      >
      > unix aix
      >
      > http://code.google.com/p/vim/issues/detail?id=137
      >
      >
      >
      > The stack provided is not very useful unfortunately.
      >
      > The debugger is not able to show the stack beyond the signal
      >
      > handler 'deathtrap' somehow.
      >
      >
      >
      > I would suggest to comment out the set up of this signal handler, and try
      >
      > to reproduce the bug. The stack trace will then hopefully be more useful.
      >
      > In other words, try to comment out the line "catch_signals(deathtrap,
      >
      > SIG_ERR);" in os_unix.c:1332 as follows:
      >
      >
      >
      > diff -r fcd8be759157 src/os_unix.c
      >
      > --- a/src/os_unix.c Fri Jun 21 18:31:23 2013 +0200
      >
      > +++ b/src/os_unix.c Sat Jun 22 06:23:29 2013 +0200
      >
      > @@ -1329,7 +1329,7 @@
      >
      > /*
      >
      > * Arrange for other signals to gracefully shutdown Vim.
      >
      > */
      >
      > - catch_signals(deathtrap, SIG_ERR);
      >
      > + /* catch_signals(deathtrap, SIG_ERR); */
      >
      >
      >
      > #if defined(FEAT_GUI) && defined(SIGHUP)
      >
      > /*
      >
      >
      >
      >
      >
      > Then provide the stack again.
      >
      >
      >
      > I don't have IBM AIX so I cannot reproduce this. But I used
      >
      > IBM AIX a long time ago and I remember one difference with Linux:
      >
      > malloc(0) returned NULL on AIX whereas malloc(0) returns a
      >
      > valid address of 0 allocated bytes on Linux. Well, I see that
      >
      > Vim lalloc() treats 0 size allocation as error so I don't think
      >
      > that's the issue anyway.
      >
      >
      >
      > I also see that you're also using Vim-7.3.754. The latest version
      >
      > is Vim-7.3.1224. It would be best to reproduce it with the latest
      >
      > version if possible, in case the bug has already been fixed.
      >
      > You could also try to download the latest Vim with Mercurial:
      >
      >
      >
      > $ hg clone https://vim.googlecode.com/hg/ vim
      >
      >
      >
      >
      >
      >
      >
      > --
      >
      > 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

      Hello,
      I comment out the line "catch_signals(deathtrap, SIG_ERR);" in os_unix.c and compiled.
      Now in dbx i have the stack:
      Segmentation fault in extend_brk at 0xd0129178 ($t1)
      0xd0129178 (extend_brk+0x238) 90040004 stw r0,0x4(r4)
      (dbx) where
      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
      extend_brk(internal error: assertion failed at line 3550 in file frame.c
      ??, internal error: assertion failed at line 3550 in file frame.c
      ??, internal error: assertion failed at line 3550 in file frame.c
      ??) at 0xd0129178
      (dbx)

      --
      --
      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+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Show all 11 messages in this topic