Re: [HACKERS] patch for memory overrun on Linux(i386) - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] patch for memory overrun on Linux(i386)
Date
Msg-id Pine.BSF.3.96.980321212527.324F-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] patch for memory overrun on Linux(i386)  (ocie@paracel.com)
List pgsql-hackers
On Sat, 21 Mar 1998 ocie@paracel.com wrote:

> Maurice Gittens wrote:
> >
> > Hi,
> >
> > It turns of that one of the bugs I detected with Electric Fence
> > is caused by an assumption that memory return by palloc and malloc
> > is aligned on 8 bytes boundaries (double alignment).
> > Adjusting this to correspond with the reality of the malloc
> > implementation on my pentium based linux box fixes the problem.
> >
> > The following simple patch to include/utils/memutils.h
> > will fix the problem.
> >
> > 85c85
> > < #if ! defined(sco)
> > ---
> > > #if ! defined(sco) && !defined(linux)
>
> I may be off on this one, but I thought that memory alignment was a
> cpu, and not necessarily an OS issue.  I.E. Solaris x86 might show the
> "misalignment", while Linux Alpha would not.

    Ummm...you are comparing both two different CPU and two different
OSs here...more appropriately to your argument would be Linux/x86 vs
Linux/Alpha, wouldn't it?  If it was a CPU issue...?

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


pgsql-hackers by date:

Previous
From: Mattias Kregert
Date:
Subject: Re: sched_yield()
Next
From: The Hermit Hacker
Date:
Subject: Re: sched_yield()