From the ktrace output it looks like the alpha is confused about
the datasize limit calculation. The program data appears to start
at the 4G mark so it is likely that the confusion is with the
'data_addr' variable whos calculation was changed slightly.
In that rev data_addr was set to the first data segment's address.
In the original code the data_addr was set to the last data segment's
address.
Try making the following change, from:
if (prot & VM_PROT_WRITE) {
data_size += seg_size;
if (data_addr == 0)
data_addr = seg_addr;
} else {
text_size += seg_size;
if (text_addr == 0)
text_addr = seg_addr;
}
To:
if (prot & VM_PROT_WRITE) {
data_size += seg_size;
data_addr = seg_addr;
} else {
text_size += seg_size;
if (text_addr == 0)
text_addr = seg_addr;
}
And see if that fixes the problem. I'm not sure why the alpha
is separating its first and last data segments by 4G of VM, some
debugging would be helpful:
if (prot & VM_PROT_WRITE) {
printf("LOAD DATASEG %p %ld\n", (void *)seg_addr,
seg_size);
data_size += seg_size;
if (data_addr == 0)
data_addr = seg_addr;
} else {
printf("LOAD TEXTSEG %p %ld\n", (void *)seg_addr,
seg_size);
text_size += seg_size;
if (text_addr == 0)
text_addr = seg_addr;
}
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
