Bug#580961: vim: killing vim results in a segfault

2010-05-21 Thread Bernd Zeimetz
On 05/20/2010 07:07 AM, James Vega wrote: On Mon, May 10, 2010 at 10:40:06AM +0200, Bernd Zeimetz wrote: Although this does not happen when I run vim with -u NONE -U NONE, I think it is still worth to report this segfault as the vim code should be robust enough to handle even broken configs

Bug#580961: vim: killing vim results in a segfault

2010-05-19 Thread James Vega
On Mon, May 10, 2010 at 10:40:06AM +0200, Bernd Zeimetz wrote: Although this does not happen when I run vim with -u NONE -U NONE, I think it is still worth to report this segfault as the vim code should be robust enough to handle even broken configs without segfaulting while receiving a

Bug#580961: vim: killing vim results in a segfault

2010-05-12 Thread James Vega
On Mon, May 10, 2010 at 05:54:00PM -0400, James Vega wrote: On Mon, May 10, 2010 at 01:55:16PM +0200, Bernd Zeimetz wrote: On 05/10/2010 01:51 PM, James Vega wrote: On Mon, May 10, 2010 at 10:40:06AM +0200, Bernd Zeimetz wrote: Although this does not happen when I run vim with -u NONE -U

Bug#580961: vim: killing vim results in a segfault

2010-05-10 Thread Bernd Zeimetz
Package: vim Version: 2:7.2.330-1 Severity: normal Although this does not happen when I run vim with -u NONE -U NONE, I think it is still worth to report this segfault as the vim code should be robust enough to handle even broken configs without segfaulting while receiving a sigterm. I have

Bug#580961: vim: killing vim results in a segfault

2010-05-10 Thread James Vega
On Mon, May 10, 2010 at 10:40:06AM +0200, Bernd Zeimetz wrote: Although this does not happen when I run vim with -u NONE -U NONE, I think it is still worth to report this segfault as the vim code should be robust enough to handle even broken configs without segfaulting while receiving a

Bug#580961: vim: killing vim results in a segfault

2010-05-10 Thread Bernd Zeimetz
On 05/10/2010 01:51 PM, James Vega wrote: On Mon, May 10, 2010 at 10:40:06AM +0200, Bernd Zeimetz wrote: Although this does not happen when I run vim with -u NONE -U NONE, I think it is still worth to report this segfault as the vim code should be robust enough to handle even broken configs

Bug#580961: vim: killing vim results in a segfault

2010-05-10 Thread James Vega
On Mon, May 10, 2010 at 01:55:16PM +0200, Bernd Zeimetz wrote: On 05/10/2010 01:51 PM, James Vega wrote: On Mon, May 10, 2010 at 10:40:06AM +0200, Bernd Zeimetz wrote: Although this does not happen when I run vim with -u NONE -U NONE, I think it is still worth to report this segfault as the