This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author meador.inge
Recipients mancausoft, mark.dickinson, meador.inge
Date 2011-09-12.17:40:09
SpamBayes Score 7.4277196e-11
Marked as misclassified No
Message-id <CAK1Qooqvfn9t00ZnoTQg6b=o650p5aRKDRBR=79M6mZLqEEL9Q@mail.gmail.com>
In-reply-to <1315829413.2.0.530868416285.issue7201@psf.upfronthosting.co.za>
Content
On Mon, Sep 12, 2011 at 7:10 AM, Mark Dickinson <report@bugs.python.org> wrote:

> Mark Dickinson <dickinsm@gmail.com> added the comment:
>
> I believe the problem is specific to machines still using the old ABI ('OABI').  Which ABI was being used on your test machine?

I tested the new ABI (armel).  I will try the old ABI.  However, after
reading over the ABI differences, the problems seem to be expected.
In particular:

"""
Struct packing and alignment

With the new ABI, default structure packing changes, as do some
default data sizes and alignment (which also have a knock-on effect on
structure packing). In particular the minimum size and alignment of a
structure was 4 bytes. Under the EABI there is no minimum and the
alignment is determined by the types of the components it contains.
This will break programs that know too much about the way structures
are packed and can break code that writes binary files by dumping and
reading structures.
"""

Once I get an OABI system up and running I will substantiate that
claim.  I don't think there is going to be a bug fix here as I don't
think it is practical to support both ABIs.  Just a "these tests are
expected to fail due to ABI differences x, y, z" kind of thing.
History
Date User Action Args
2011-09-12 17:40:10meador.ingesetrecipients: + meador.inge, mark.dickinson, mancausoft
2011-09-12 17:40:10meador.ingelinkissue7201 messages
2011-09-12 17:40:09meador.ingecreate