Bug#684716: Bug#678525: GCC bug

2012-08-14 Thread Rahul Amaram
James, thanks for pointing out this. You are right. Using Py_ssize_t* instead of int* has indeed fixed the problem. We somehow were misguided reg. the problem. Thanks once again for taking the time to look into this. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subjec

Bug#684716: Bug#678525: GCC bug

2012-08-13 Thread James Y Knight
It's not a bug in GCC. It's a bug in the code. The second call to PyArg_ParseTuple passes an int* where a Py_ssize_t* should be passed. (The &data_len argument). -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb