memory addressing

hsbackup_at_gmail.com
Date: 01/27/05


Date: 26 Jan 2005 15:44:03 -0800

The linux port of XSB, (http://xsb.sf.net), has stopped working with
kernel versions > 2.6.9. XSB has been using the highest bit in the
memory address for tagging. This seems to cause a segmentation fault.
What changed in the linux memory managment between 2.6.8 and 2.6.9? XSB
does have the capability of stealing other bits of an address word for
tagging, how can i figure out which ones are safe. Assume we only need
to build XSB for systems with less than 1Gb of physical memory. TIA.



Relevant Pages

  • memory addressing
    ... The linux port of XSB,, has stopped working with ... XSB has been using the highest bit in the ... What changed in the linux memory managment between 2.6.8 and 2.6.9? ... tagging, how can i figure out which ones are safe. ...
    (comp.os.linux.development.apps)
  • memory addressing
    ... The linux port of XSB,, has stopped working with ... XSB has been using the highest bit in the ... What changed in the linux memory managment between 2.6.8 and 2.6.9? ... tagging, how can i figure out which ones are safe. ...
    (comp.os.linux.misc)
  • Re: memory addressing
    ... > tagging, how can i figure out which ones are safe. ... > to build XSB for systems with less than 1Gb of physical memory. ... But even on the old kernel ...
    (comp.os.linux.development.apps)