So I'm still getting this one, or something pretty similar, every time my
ssh session drops:
7ffe71ba798a _ndoprnt_s () + 1a
7ffe71ba7932 _ndoprnt () + 12
7ffe71ba6bdd vsnprintf () + ad
7ffe71ba5df3 vasprintf () + 43
7ffe71ba5f9c asprintf () + 9c
7ff
Danek Duvall wrote:
> On Fri, Jun 10, 2016 at 07:49:30PM +0200, Bram Moolenaar wrote:
>
> > Thanks for the stack trace. I'll make a patch to block autocommands in
> > deathtrap(), that should avoid this crash. Obviously it won't exit
> > completely cleanly, but that's very difficult to avoid.
On Fri, Jun 10, 2016 at 07:49:30PM +0200, Bram Moolenaar wrote:
> Thanks for the stack trace. I'll make a patch to block autocommands in
> deathtrap(), that should avoid this crash. Obviously it won't exit
> completely cleanly, but that's very difficult to avoid.
True. Though in the case of TE
Danek Duvall wrote:
> > > I've been chasing down a bug in vim, where killing vim (usually via SIGHUP
> > > or SIGTERM) causes it to get a SIGSEGV and dump core. I'm doing my work
> > > on
> > > Solaris, but I can get it to do the same thing on Ubuntu 14.04, so it's
> > > not
> > > strictly a S
On Thu, Jun 09, 2016 at 10:53:16PM +0200, Bram Moolenaar wrote:
> Danek Duvall wrote:
>
> > I've been chasing down a bug in vim, where killing vim (usually via SIGHUP
> > or SIGTERM) causes it to get a SIGSEGV and dump core. I'm doing my work on
> > Solaris, but I can get it to do the same thing
James McCoy wrote:
> On Thu, Jun 09, 2016 at 10:53:16PM +0200, Bram Moolenaar wrote:
> >
> > Danek Duvall wrote:
> > > The thought I have was to do the classic thing where the signal handler
> > > sets a global flag and returns immediately. For the majority of the cases
> > > I've seen, the loo
On Thu, Jun 09, 2016 at 10:53:16PM +0200, Bram Moolenaar wrote:
>
> Danek Duvall wrote:
> > The thought I have was to do the classic thing where the signal handler
> > sets a global flag and returns immediately. For the majority of the cases
> > I've seen, the loop in RealWaitForChar is where the
Danek Duvall wrote:
> I've been chasing down a bug in vim, where killing vim (usually via SIGHUP
> or SIGTERM) causes it to get a SIGSEGV and dump core. I'm doing my work on
> Solaris, but I can get it to do the same thing on Ubuntu 14.04, so it's not
> strictly a Solaris thing.
Hmm, killing Vi
I've been chasing down a bug in vim, where killing vim (usually via SIGHUP
or SIGTERM) causes it to get a SIGSEGV and dump core. I'm doing my work on
Solaris, but I can get it to do the same thing on Ubuntu 14.04, so it's not
strictly a Solaris thing.
Most reproducibly (for me, at least), it seem
