[Python-Dev] problem with pymalloc on the BeOS port.

["Martin v. Löwis"]

Tim Peters wrote:

>>Any clue ?
> 
> 
> Try gcc without -O.  Nobody has reported anything like this before --
> you're in for a lot of fun <wink>.

In addition, try to find out whether BeOS' malloc is somehow "strange".
Does the system have the notion of a linear address space? Does it do
pages? and so on. If you find a feature that you wouldn't expect in
Windows NT, Linux, or HP-UX (*), that might give a clue.

Regards,
Martin

(*) I did not expect the Spanish Inquisition.