Matan,
Thanks for you reply.... You were right, nearly all the errors are due to Valgrind
not recognising the svgalib ioctl's.... Do you have a list of the ioctl numbers that
svgalib supplies?
Thanks,
James
On Sun, 9 Feb 2003 13:47:25 -0600
Matan Ziv-Av <[EMAIL PROTECTED]> wrote:
> On Sun, 9 Feb 2003, James Wright wrote:
>
> > int __svgalib_pci_read_config_dword(int pos, int address)
> > {
> > pcic_t p;
> > p.pcipos = pos;
> > p.address = address;
> > p.val = 0; /*********** I INSERTED THIS LINE to initialise the return value
>***********/
> > if(ioctl( __svgalib_mem_fd, SVGALIB_HELPER_IOCGPCIINL, &p)) return -1;
> > return p.val;
> > };
> >
> > Is that the correct thing to do???Shal i go through as many errors as i can with
>"valgrind"
> > to try and clean it up? or is this a waste of time????
>
> It's not a waste of time, but if you want to do it, you will need to
> spend a lot of time.
> The correct thing to do is to teach valgrind about svgalib's ioctls, so
> it knows which values are read/written by those calls.
>
>
> --
> Matan Ziv-Av. [EMAIL PROTECTED]
>
>
>
> ------------------------------------------------------------------
> Unsubscribe: To: [EMAIL PROTECTED]
> Body: unsubscribe linux-svgalib
>
------------------------------------------------------------------
Unsubscribe: To: [EMAIL PROTECTED]
Body: unsubscribe linux-svgalib
