linuxolator: amd64 Linux Test Project failures

[Scot Hetzel]

On 12/30/06, Divacky Roman <xdivac02 at stud.fit.vutbr.cz> wrote:
> > I just added another %p to the format, here are my results with all of
> > the debugging printfs.
> >
> > Dec 29 15:32:38 hp010 kernel: linux(1807): access(Checking if path
> > [0xffffffffffffffff/0xffffffffa3bc8be0/0x28069000] exists) <-
> > &args-path, args-path
>
> the access03 test passes 0 as the path address. interesting that it
> gets this non-0 address. is the address consistent among runs?
> I wonder if glibc mangles it somehow (it shouldnt but you never know)
>
Two seperate runs, and it gives the same results in both:

Dec 30 10:11:33 hp010 kernel: linux(45040): access(Checking if path
[0xffffffffffffffff/0xffffffffa41f7be0/0x28063000] exists)
Dec 30 10:11:33 hp010 kernel: kern_alternate_path: error = 0, path =
0xffffffffa41f7980/0x28063000
Dec 30 10:11:33 hp010 kernel: linux(45040): __func__(Path checked: error = 22)
Dec 30 10:11:33 hp010 kernel: linux(45040): access(Checking
kern_access: path = 0xffffffffa41f7b18)

Dec 30 10:12:31 hp010 kernel: linux(45042): access(Checking if path
[0xffffffffffffffff/0xffffffffa3abfbe0/0x28063000] exists)
Dec 30 10:12:31 hp010 kernel: kern_alternate_path: error = 0, path =
0xffffffffa3abf980/0x28063000
Dec 30 10:12:31 hp010 kernel: linux(45042): __func__(Path checked: error = 22)
Dec 30 10:12:31 hp010 kernel: linux(45042): access(Checking
kern_access: path = 0xffffffffa3abfb18)

> can you try simple program like
>
> main()
> {
>    access(0, 0);
> }
>
> and show its output?
>
Dec 30 10:02:42 hp010 kernel: linux(44990): access(Checking if path
[0xffffffffffffffff/0xffffffffa42d3be0/0] exists)
Dec 30 10:02:42 hp010 kernel: kern_alternate_path: error = 14, path =
0xffffffffa42d3980/0

Scot
-- 
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.