Fw: 32 bit to 64 bit migration of C-API(Python)
Hi,
I am working in Python-C ApI (Integrated Project). The Project has migrated to 64 bit machine from 32 bit machine. Every thing was working fine in 32 bit machine. But we getting following error in 64 bit machine. " Python int too large to convert to C long".
When I start debug the code and found that we are using long variable which has size of 8 bit in C code. If I replace long to int32_t variable in C and all long value become garbage and I got index out of error from Python.The reason to become garbage value of long(after int conversion),we are using lot of Place Python api which give the long result and we use in further process like ( write/reading file).I have tried to replace with int but it did not work. I am not sure really this is only reason but it may be one of the reason to get the above error.I have also done google search but not able to get exact reason. After spending 3 days,I am not able to figure out the solution of this issue. Does anyone provide some insight. we are using Python 2.7.2 and Gcc : 4.7.0 Please let me know if I need to provide more info. Your earlier response will help us lot as we need to fix this issue as soon as possible.( it is kind of blockage for us) Thanks Abhishek Goswami Bangalore Phone No -07829580867 Skype : abhishekgoswami1
On 27.01.2013 07:35, abhishek goswami wrote:
Hi,
I am working in Python-C ApI (Integrated Project). The Project has migrated to 64 bit machine from 32 bit machine. Every thing was working fine in 32 bit machine. But we getting following error in 64 bit machine. " Python int too large to convert to C long".
I suppose you're on Windows. Windows longs are still 32-bit, even on 64-bit platforms, so it's possible that you see overflow errors such as the above when dealing with large integers.
You should be getting the same errors on your 32-bit builds, though, so it's probably a good idea to check why you are not seeing them there.
No,I am on linux machine
Thanks Abhishek Goswami Bangalore Phone No -07829580867/9962270999 Skype : abhishekgoswami1
From: M.-A. Lemburg mal@egenix.com To: abhishek goswami zeal_goswami@yahoo.com Cc: "capi-sig@python.org" capi-sig@python.org Sent: Monday, 28 January 2013 3:06 PM Subject: Re: [capi-sig] Fw: 32 bit to 64 bit migration of C-API(Python)
On 27.01.2013 07:35, abhishek goswami wrote:
Hi,
I am working in Python-C ApI (Integrated Project). The Project has migrated to 64 bit machine from 32 bit machine. Every thing was working fine in 32 bit machine. But we getting following error in 64 bit machine. " Python int too large to convert to C long".
I suppose you're on Windows. Windows longs are still 32-bit, even on 64-bit platforms, so it's possible that you see overflow errors such as the above when dealing with large integers.
You should be getting the same errors on your 32-bit builds, though, so it's probably a good idea to check why you are not seeing them there.
abhishek goswami zeal_goswami@yahoo.com writes:
I am working in Python-C ApI (Integrated Project). The Project has migrated to 64 bit machine from 32 bit machine. Every thing was working fine in 32 bit machine. But we getting following error in 64 bit machine. " Python int too large to convert to C long".
When I start debug the code and found that we are using long variable which has size of 8 bit in C code. If I replace long to int32_t variable in C and all long value become garbage[...]
I find it hard to follow your debugging efforts from this point.
It is clear that you are getting the error in 64-bit builds. The next thing one would do is try to figure out where the error comes from. After all, the overflow exception is hardly magic, it is raised in exactly one place in Python source code, the PyLong_AsLong function, in the case when the Python integer is too large to fit in a C long.
Changing the type from long to int32_t and other things you are trying will not fix the bug. Your problem is the number that is too large to fit in a long in the first place -- find where it's coming from and fix it. For example, you can examine the stack trace and see which Python integer of value outside [2**63, 2**63) is attempted to be converted to long. If your project calls PyLong_AsLong, annotate all calls to that function with prints that show the repr of the value passed. Formats like "%d" are also suspicious. If all else fails, rebuild Python with -g and put a breakpoint on the line of PyLong_AsLong that handles the overflow.
participants (3)
-
abhishek goswami -
Hrvoje Niksic -
M.-A. Lemburg