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-bugs-dist-requ...@lists.debian.org
with a
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-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
Thanks for the additional information Fredrik. Your analysis was really
helpful. Could you please raise a new Debian GCC bug? If they fix it,
then we'll have no need to make any changes in calendarserver Debian.
Else we will have to force compilation of the package with gcc 4.6.
--
To UNSUBSC
On 08/13/2012 02:58 PM, Rahul Amaram wrote:
Thanks for the additional information Fredrik. Your analysis was really
helpful. Could you please raise a new Debian GCC bug? If they fix it,
then we'll have no need to make any changes in calendarserver Debian.
Else we will have to force compilation of
Hi,
After further analyzing the problem and with help from Glyph Lefkowitz,
Chris Cleeland and Rahul Amaram, I managed to create a test case that
proved it is a gcc bug.
The included tar file includes a simple testcase that can be run
under Debian.
The c file that is the base for this bugrep
5 matches
Mail list logo
