On Sun, Jun 09, 2013 at 03:29:43PM +0200, Dominique Pellé wrote:
> Hi
>
> These valgrind error are annoying but they are not a bug.
> They should not cause a crash. See this document that
> describes why:
>
> http://svn.python.org/view/python/trunk/Misc/README.valgrind?view=markup
> --without-pymal
Simon Ruderich wrote:
> On Fri, Jun 07, 2013 at 05:55:06PM +0900, Jun T. wrote:
>> Thank you for your reply; it is always nice to hear I'm not alone.
>> And thank you for your test.
>>
>> I did some test by myself and noticed that if I configure with
>>
>> --enable-pythoninterp=dynamic and/or -
On Fri, Jun 07, 2013 at 05:55:06PM +0900, Jun T. wrote:
> Thank you for your reply; it is always nice to hear I'm not alone.
> And thank you for your test.
>
> I did some test by myself and noticed that if I configure with
>
> --enable-pythoninterp=dynamic and/or --enable-python3interp=dynamic
>
On 2013/06/07, at 6:08, Elimar Riesebieter wrote:
> * Jun T. [2013-06-06 10:39 +0900]:
>> I'm getting core dump (segfault) in test86;
>> vim 7.3.1128 on Mac OS X and Linux, both with Python 2.7/64bit.
>> Does this happen only to me?
>
> Me too :-(
Thank you for your reply; it is always nice to
Hi all. I'm new to this list.
I'm getting core dump (segfault) in test86;
vim 7.3.1128 on Mac OS X and Linux, both with Python 2.7/64bit.
Does this happen only to me?
It seems that the problem is in OutputWritelines().
PyArg_Parse(..., "et#",.., &len) returns a bogus value for len,
because len is
