Re: shared memory load address and gcl

2010-02-03 Thread Camm Maguire
Greetings, and thank you *so much* for your clear and helpful reply. I will instruct the linker script as you say for the next upload. This issue primarily was a configuration issue on kamd64 8.0, as the ceiling address to the heap was determined to be too low unnecessarily. Configuring the addre

Re: Installer status - error from 3.2.2010

2010-02-03 Thread Petr Salinger
Hi. Installations goes with every possible default settings - only enter and continue - basic install with 72 packages (system utilities) After system reboot: "Trying to mount root from ufs:/dev/ad0s1 panic: vm_fault: fault on nofault entry: d2afa000 Cannot dump. No dump device defined." In

Installer status - error from 3.2.2010

2010-02-03 Thread Anton Andreev
Hello, Installations goes with every possible default settings - only enter and continue - basic install with 72 packages (system utilities) After system reboot: "Trying to mount root from ufs:/dev/ad0s1 panic: vm_fault: fault on nofault entry: d2afa000 Cannot dump. No dump device defined." In

Re: shared memory load address and gcl

2010-02-03 Thread Petr Salinger
Hi. I think my conceptual question is now clearer. My experience with linux tells me that sbrk'ed memory cannot overrun the address used for shared memory maps. But on asdfasdf, there appears at first blush no such problem. Can this possibly be right? Should I ignore this apparent ceiling to