Hello,
There’s three way to perform an invalid memory access :
The attempt to execute/jump at an invalid address.
The attempt to read at an invalid address.
The attempt to write at an invalid address.
Determining the execute case with rt_sigaction is easy : the last value
of eip match the valu
Le 2017-03-27 17:30, Richard Weinberger a écrit :
On Mon, Mar 27, 2017 at 4:45 PM, none wrote:
Hello,
There’s three way to perform an invalid memory access :
The attempt to execute/jump at an invalid address.
The attempt to read at an invalid address.
The attempt to write at an invalid
Hello,
I wanted to known the rules in coding guidelines concerning the use of
size_t.
It seems the signed int type is used most of the time for representing
string sizes, including in some parts written by Linus in /lib.
They’re can buffer overflows attack if ssize_t if larger than
sizeof(int)
Le 2016-10-14 01:37, Al Viro a écrit :
On Fri, Oct 14, 2016 at 12:12:43AM +0200, none wrote:
Hello,
I wanted to known the rules in coding guidelines concerning the use of
size_t.
It seems the signed int type is used most of the time for representing
string sizes, including in some parts
On Fri, February 11, 2005 11:18 am, Larry McVoy said:
The mails have started flowing in saying "I don't agree with Alexandre
and please don't pull the plug" so a point of clarification. We have
no intention of shutting down the BK free product. We are aware that
there are 10's of thousands of dev
5 matches
Mail list logo
