Re: [Valgrind-users] Syscall/ioctl wrappers

[Subhashish P. <sp...@gm...>]

On Mon, Mar 24, 2014 at 3:15 PM, Tom Hughes <to...@co...> wrote:
> On 24/03/14 09:37, Subhashish Pradhan wrote:
>
>> 1 - It was mentioned "it may well be that no memory is read/written,
>> but you'd have to look at the kernel and see what that ioctl does to
>> be sure." Does it mean using strace or looking at kernel logs using
>> dmesg?
>
>
> It means reading the kernel source to see what that ioctl does and what
> memory it accesses.

...

> Porting valgrind to a new platform is a major undertaking so you really need
> to start by reading the code carefully and understanding it all works. If
> you try and understand it by asking questions about every little detail here
> it will be very painful...
>

...

> All that should have been pretty obvious from reading one of them though,
> which is exactly what I just had to do to answer your question, as they have
> lots of comments in explaining what is going on.
>
>
> Tom
>
> --
> Tom Hughes (to...@co...)
> http://compton.nu/


I think I'd have to really go through the source and work them out
rather than getting the gist from documentation and stopping there.

But may I come back here to ask about the correctness of an
implementation or patch in future if I'm able to do that?

Regards,
Subhashish Pradhan