Re: [Valgrind-users] Teaching valgrind..

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

Hello again,

One last query: Are the kernel traps also implemented there in coregrind or
somewhere else?

May  I have the location like that for syscalls?

Regards,
Subhashish


On Fri, Jan 10, 2014 at 5:06 PM, Subhashish Pradhan <sp...@gm...>wrote:

> Thanks so much! I googled a lot but couldn't even find a hint about it.
>
> I would take a look into coregrind/m_syswrap/syswrap-generic.c and ask my
> doubts on #valgrind-dev.
>
> Regards,
> Subhashish
>
>
> On Fri, Jan 10, 2014 at 2:56 AM, Philippe Waroquiers <
> phi...@sk...> wrote:
>
>> On Thu, 2014-01-09 at 19:40 +0530, Subhashish Pradhan wrote:
>> > Hello!
>> >
>> >
>> > I have some theoretical queries. What does "teaching valgrind some
>> > syscalls" mean?
>> >
>> >
>> > What are the read and write primitives of valgrind and where are they
>> > handled?
>> Basically, 'teaching a (new) syscall to valgrind' means to write a
>> wrapper for this syscall. The wrapper describes the effect of the
>> syscall (typically, for memcheck, describes what memory is read
>> by the syscall, and what memory is written by the syscall).
>>
>> The easiest to undersatnd all that is to look at some existing
>> wrappers e.g. in coregrind/m_syswrap/syswrap-generic.c
>>
>> Philippe
>>
>> NB: valgrind-developers might have been a better mailing list for this
>> question, as writing a syscall wrapper is more a valgrind dev activity.
>>
>>
>>
>