python crash on windows but not on linux

[Peter Otten]

hjebbers wrote:

> On Feb 12, 3:17 pm, Peter Otten <__pete... at web.de> wrote:
>> hjebbers wrote:
>> > On Feb 11, 7:01 pm, Peter Otten <__pete... at web.de> wrote:
>> >> hjebbers wrote:
>> >> > On Feb 11, 5:45 pm, M3RT <mgul... at gmail.com> wrote:
>> >> >> The problem may be related to how you treat the EDI file or lets
>> >> >> say DATA. Also your coding style is important. Can you provide more
>> >> >> info?
>>
>> >> > Yes, a whole lot more; but I do not want to bother you with that
>> >> > now. I was just wondering if it is possible that the same setup
>> >> > gives a CRASH! on windows and just works on linux.
>> >> > (where is the bug?)
>>
>> >> In the platform-specific code ;)
>>
>> >> Even on alt.haruspicy they cannot do much without a liver now and
>> >> then...
>>
>> > if it is in the platform-specific code should I make this into a
>> > bugreport?
>>
>> A this stage a bug report would be useless. The details you have provided
>> so far don't give anyone without physical access to your machine a chance
>> to reproduce the error.
>>
>> > (because the crash does not appear at the same place in my code (when
>> > doing the same test-run) it will be quite hard to point down....)
>>
>> Indeed. The culprit may be an extension written in C that is overwriting
>> memory still in use by other parts of your program.
>>
>> Peter
> 
> No C extensions used. Definitely not.
> 
> As these crashes occur during stress tests, I go to the limits of the
> memory available.
> What strikes me is:
> 1. the crash on windows, but linux works OK (same test sets)
> 2. the linux box has 750Mb RAM, the windows box has 1.5Gb (twice as
> much).

Random thoughts:

If there were not enough memory Python should give a MemoryError rather than 
segfault. 

Do both systems use the same memory layout (i. e. 32 or 64bit OS, 16 or 32 
bit unicode)?

Try an alpha of Python 2.7. If you're lucky "your" bug was found 'n' fixed 
independently.

Peter