>
> This is intentional. When 'addr' equals 'vend' the overflow path is
> triggered, but then the 'vstart' and 'vend'
> values are not carried in the overflow path - making them point to no
> address. That is the reason 'addr' is used
> in the warning message to specify the restrictive range - that gets assigned
> to 'va_start' and 'va_end' in the ideal case.
>
What do you mean when you say:
"but then the 'vstart' and 'vend' values are not carried in the overflow path -
making them point to no address."
>From your commit message: "With the update, the output gets modified to
include the function parameters along with the start and end of the virtual
memory range allowed."
i see that you would like to print an allowed range. Thus an allowed
range is specified by "vstart" and "vend", i.e.:
vstart vend
<-------|------|------> vmap spase
an allocation must be served between "vstart" and "vend". So, according to
your commit message that range should be printed in case of error.
Now you print, "vend" address and "vend + size" one. I do not follow why
you need it. Could you please explain?
--
Uladzislau Rezki
