Or to upgrade GCC to a version (like the recent 4.7.1 release) that doesn't
produce bad code.
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@jamessan.com
gcc 4.7.1 still has this problem
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
On Tue, Jun 12, 2012 at 08:56:56AM -0500, Thomas Dziedzic wrote:
Just an fyi, it is still broken with this patch. It only prevents the
segfault, and doesn't fix the underlying bug.
e.g. :python print 'hi' doesn't segfault anymore, but it also doesn't
print anything which.
The only way I
On Saturday, April 14, 2012 4:36:29 PM UTC+2, Christian Brabandt wrote:
Hi Thomas!
[...]
diff --git a/src/if_py_both.h b/src/if_py_both.h
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -74,7 +74,7 @@
char *str = NULL;
int error = ((OutputObject *)(self))-error;
-if
On Tue, Jun 12, 2012 at 7:02 AM, Piotr Skamruk piotr.skam...@gmail.com wrote:
On Saturday, April 14, 2012 4:36:29 PM UTC+2, Christian Brabandt wrote:
Hi Thomas!
[...]
diff --git a/src/if_py_both.h b/src/if_py_both.h
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -74,7 +74,7 @@
char
On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic gos...@gmail.com wrote:
It looks like this was caused by
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
I will try to see if this was the problem once the next gcc snapshot
comes out (this weekend or next week) and try to report back
Hi Thomas!
On Mi, 09 Mai 2012, Thomas Dziedzic wrote:
On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic gos...@gmail.com wrote:
It looks like this was caused by
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
I will try to see if this was the problem once the next gcc snapshot
On Wed, May 09, 2012 at 01:48:59AM -0500, Thomas Dziedzic wrote:
On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic gos...@gmail.com wrote:
It looks like this was caused by
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
I will try to see if this was the problem once the next gcc
On Wed, May 9, 2012 at 4:29 AM, Christian Brabandt cbli...@256bit.org wrote:
Hi Thomas!
On Mi, 09 Mai 2012, Thomas Dziedzic wrote:
On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic gos...@gmail.com wrote:
It looks like this was caused by
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
On Apr 19, 2012 8:02 PM, Ernie Rael e...@raelity.com wrote:
On 4/19/2012 3:59 PM, Thomas Dziedzic wrote:
Ok, I'm getting closer to figuring this out, it's caused by having the
-O2 flag there. If you remove -O2 from CFLAGS, there is no crash. I'm
guessing this has something to do with gcc
It looks like this was caused by
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
I will try to see if this was the problem once the next gcc snapshot
comes out (this weekend or next week) and try to report back here.
--
You received this message from the vim_dev maillist.
Do not top-post!
On Thu, Apr 19, 2012 at 12:02 PM, Thomas Dziedzic gos...@gmail.com wrote:
On Sun, Apr 15, 2012 at 9:44 AM, Bram Moolenaar b...@moolenaar.net wrote:
Christian Brabandt wrote:
On Fr, 13 Apr 2012, Thomas Dziedzic wrote:
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg tmhedb...@gmail.com
On 4/19/2012 3:59 PM, Thomas Dziedzic wrote:
Ok, I'm getting closer to figuring this out, it's caused by having the
-O2 flag there. If you remove -O2 from CFLAGS, there is no crash. I'm
guessing this has something to do with gcc 4.7.0 possibly
While it may be an optimizer bug, and things like
On Sat, Apr 14, 2012 at 02:52:16PM -0500, Thomas Dziedzic wrote:
On Sat, Apr 14, 2012 at 1:56 PM, lilydjwg lilyd...@gmail.com wrote:
On Sat, Apr 14, 2012 at 12:27:55PM -0500, Thomas Dziedzic wrote:
[...]
It seems that str is for some reason getting set to null even if
everything appears
Christian Brabandt wrote:
On Fr, 13 Apr 2012, Thomas Dziedzic wrote:
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with +python but not +python3, if that makes any difference.
On Fri, Apr 13, 2012 at 09:38:36AM -0500, Thomas Dziedzic wrote:
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with +python but not +python3, if that makes any difference.
Hi,
I
On Friday, April 13, 2012 7:38:36 AM UTC-7, Thomas Dziedzic wrote:
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg wrote:
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with +python but not +python3, if that makes any difference.
Hi,
I was going to report
Hi Thomas!
On Fr, 13 Apr 2012, Thomas Dziedzic wrote:
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with +python but not +python3, if that makes any difference.
Hi,
I was going
On Sat, Apr 14, 2012 at 9:36 AM, Christian Brabandt cbli...@256bit.org wrote:
Hi Thomas!
On Fr, 13 Apr 2012, Thomas Dziedzic wrote:
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with
On Sat, Apr 14, 2012 at 12:27:55PM -0500, Thomas Dziedzic wrote:
[...]
It seems that str is for some reason getting set to null even if
everything appears to be ok..
Nick's comment also makes me think it might possibly have something to
do with the recent gcc 4.7 update.
Hi, I just upgraded
On Sat, Apr 14, 2012 at 1:56 PM, lilydjwg lilyd...@gmail.com wrote:
On Sat, Apr 14, 2012 at 12:27:55PM -0500, Thomas Dziedzic wrote:
[...]
It seems that str is for some reason getting set to null even if
everything appears to be ok..
Nick's comment also makes me think it might possibly have
On Fri, Apr 13, 2012 at 01:07:27AM -0700, William E. Skeith III wrote:
Hello,
I am writing to report a potential bug. To reproduce:
:python print hello
This gives me a segmentation fault. A few other arch linux users have
confirmed the issue, and noted that other python commands
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with +python but not +python3, if that makes any difference.
pgpCk5WPS8cqx.pgp
Description: PGP signature
On Fri, Apr 13, 2012 at 9:00 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Arch x86_64 here and I can reproduce the segfault as well. My Vim is
compiled with +python but not +python3, if that makes any difference.
Hi,
I was going to report this when I had more time to debug, but since
people
23 matches
Mail list logo
