Memory fault - core dumped while compiling 2.2.1 on SCO

Martin v. Loewis martin at v.loewis.de
Thu Sep 5 00:50:43 CEST 2002


Anton Graph <aglyportREMOvethispart at nospam.yahoo.com> writes:

> python -E setup.py build in gdb:
> 
> (gdb) where
> #0  0x80016d06 in do_reloc () from /usr/lib/libc.so.1

That sounds like a question to bring to an SCO forum. Apparently, this
crashes when doing relocations while loading the extension
module. This raises a number of questions:

- Why does it do relocations at all? Could it be that you have object
  files that a not position-independent? I.e. is distutils using the
  compiler correctly both for compilation, and for linking?

  It might be correct that it tries to perform relocation, e.g. for
  the global offset table, and the procedure linkage table - but it
  *is* troubling that relocations is where it crashes.

- What is the precise version of the operating system you are using?

- I'm troubled by the fact that in both configurations (with an
  without gcc), the compiler is always referred-to as "cc". Are you
  sure you are not using gcc?

  Please have a look at

  http://gcc.gnu.org/ml/gcc-testresults/1999-04/msg00239.html

  Notice that the failure mode is quite similar... Likewise,

  http://www.bitmechanic.com/mail-archives/dbi-users/Jun1999/0485.html

  reports such a problem when using gcc on SCO.

Regards,
Martin



More information about the Python-list mailing list