Re: Are bad developer libraries the problem with M$ software?

"" wrote:

> As a follow-up to my post, where I said:

It's nothing to do with the stack; arrays in the data segment are no different to arrays on the stack.

The size of an array is the product of the number of elements and the size of each element. The size of a pointer is fixed, and is normally the same as the platform's "word size" (e.g. 2, 4 or 8 bytes for 16, 32 and 64 bit platforms respectively).

However, it's easy to get confused by the various ways in which C treats arrays and pointers as being equivalent. E.g. arrays are always passed by reference (as a pointer to the start of the array). If you declare a function's argument as an array, e.g.

        void foo(char arg[])

it's actually a pointer.

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related securityfocus.com Links bugtraq certification focus-bsd focus-ids focus-ih focus-linux focus-ms focus-sun focus-unix-other focus-virus forensics incidents libnet linux-secnews ms-secnews pen-test secpapers secprog sectools secureshell security-basics securityjobs sf-news vuln-dev webappsec Request more information about Pantek

> Once you pass the string around to functions as a char*, or allocate

Note that you would get exactly the same result if the array "x" was in the data segment (a global variable or a "static" local variable) rather than on the stack.

-- 
Glynn Clements