Re: [Valgrind-developers] help

[Nicholas N. <nj...@cs...>]

On Mon, 4 Aug 2008, chenping19850429 wrote:

>   As I know, complier will give a warning when the type of pionter is different from the type of memory that it accesses to. Yet I want to give more detail information of the type conflict. In my opinion, some of the warnings represent  acutal  error, while others may be done by the programmer delibrately.Moreover, compiler may give no warnings in some cases. For example, if  memory is allocated with the type of "int", and an pointer with "unsigned int" type points to it.This may lead to integer overflow. So I want to use valgrind give more information about the warning, give some useful information to the programmer and tell them the potential vulnerability.
>       But I'm not sure that whether the work I mentioned above is worthy to do. So I want to  get some suggestions from you.
>       (1)Whether "pointer type checking" based on valgrind is worthy to do?
>       (2)Are there some previous tools which can give some type information of memory ?
>        Thank you.

You might find this paper interesting:

   Symbolic execution and run-time type inference for integer conversion
   errors

Available here: http://www.cs.berkeley.edu/~dmolnar/papers/papers.html

Nick