char *query[]

[gert]

Why does query[1] = www ?

int
main(void)
{
char *user="www";
char *password="";
char *database="www" ;
char *query[]={"SHOW DATABASES;"};
db(user,passwor d,database,quer y);
}

(gdb) next
12 char *query[]={"SHOW DATABASES;"};
(gdb) next
13 db(user,passwor d,database,quer y);
(gdb) print query
$5 = {0x400e25 "SHOW DATABASES;"}
(gdb) print query[0]
$6 = 0x400e25 "SHOW DATABASES;"
(gdb) print query[1]
$7 = 0x400e20 "www"
(gdb) print query[2]
$8 = 0x400e24 ""
(gdb) print query[3]
$9 = 0x400e20 "www"
(gdb) print query[4]
$10 = 0x0
(gdb)

source
----------
http://dfo.svn.sourceforge.net/viewv...74&view=markup

[Richard]

gert <ge**********@g mail.comwrites:

Why does query[1] = www ?

Because you are accessing other strings outside of the scope of your
query definition.

Query is an arry of pointers to char with only one element.

query[1] (luckily) out of the bounds of query and happens to be same as
user which is pointing to "www".

(gdb) p query[1]
$4 = 0x804844c "www"
(gdb) p user
$5 = 0x804844c "www"
(gdb)

This is platform specific and you might as well have got a crash.

[gert]

There goes my carefully thought out NASA for loop :(

for(q=0;s=query[q];q++)

Guess the only solution would be using a max value then ?

[gert]

On Jul 15, 6:47 pm, gert <gert.cuyk...@g mail.comwrote:

There goes my carefully thought out NASA for loop :(

for(q=0;s=query[q];q++)

Guess the only solution would be using a max value then ?

o wait a minute what about

char **query = {"SHOW DATABASES;", 0x0 };

(gdb) print query[4]
$10 = 0x0

How can i force a 0x0 boundary ?

[gert]

On Jul 15, 6:57 pm, gert <gert.cuyk...@g mail.comwrote:

On Jul 15, 6:47 pm, gert <gert.cuyk...@g mail.comwrote:

There goes my carefully thought out NASA for loop :(

for(q=0;s=query[q];q++)

Guess the only solution would be using a max value then ?

o wait a minute what about

char **query = {"SHOW DATABASES;", 0x0 };

(gdb) print query[4]
$10 = 0x0

How can i force a 0x0 boundary ?

victory, works like a charm :)

char *query[]={"SHOW DATABASES;",NUL L};

[Jens Thoms Toerring]

gert <ge**********@g mail.comwrote:

On Jul 15, 6:47 pm, gert <gert.cuyk...@g mail.comwrote:

There goes my carefully thought out NASA for loop :(

for(q=0;s=query[q];q++)

Guess the only solution would be using a max value then ?

o wait a minute what about

char **query = {"SHOW DATABASES;", 0x0 };

You should use NULL instead of 0x0 - NULL is null pointer
while 0x0 is an integer constant (and the representation
of a null pointer isn't necessarily all bits 0 as in 0x0).

Now you can use your loop

for (q=0;s=query[q];q++ )

since s will be set to NULL for q==1 amd thus the loop will
end without accessing a non-existing array element.

(gdb) print query[4]
$10 = 0x0

How can i force a 0x0 boundary ?

I don't know what you mean with "0x0 boundary", but you
simply aren't allowed to ty to access elements past the
end of the array and you must find a way to avoid that,
like the one you already came up with, i.e. by having a
NULL pointer as the last element that you can test for.

Regards, Jens
--
\ Jens Thoms Toerring ___ [e-mail]
\______________ ____________ http://toerring.de

[Army1987]

On Sun, 15 Jul 2007 11:18:03 -0700, Barry Schwarz wrote:

The answer to your question at the start of your post is that you have
performed so much undefined behavior that you are no longer in the
realm of C. Any discussion of query[1] might as well be held in an
astrology newsgroup.

LOL...

--
Army1987 (Replace "NOSPAM" with "email")
"Never attribute to malice that which can be adequately explained
by stupidity." -- R. J. Hanlon (?)

[Richard Heathfield]

Jens Thoms Toerring said:

gert <ge**********@g mail.comwrote:

<snip>

>char **query = {"SHOW DATABASES;", 0x0 };

You should use NULL instead of 0x0 - NULL is null pointer
while 0x0 is an integer constant (and the representation
of a null pointer isn't necessarily all bits 0 as in 0x0).

Whilst I agree that NULL is better, 0x0 will correctly initialise the
pointer to NULL even on platforms where all-bits-zero doesn't mean
NULL. The compiler is required to supply some magic if need be, to
ensure that p = 0 Does The Right Thing.

<snip>

--
Richard Heathfield <http://www.cpax.org.uk >
Email: -www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999

[Flash Gordon]

Jens Thoms Toerring wrote, On 15/07/07 18:20:

gert <ge**********@g mail.comwrote:

<snip>

>char **query = {"SHOW DATABASES;", 0x0 };

You should use NULL instead of 0x0 - NULL is null pointer
while 0x0 is an integer constant (and the representation
of a null pointer isn't necessarily all bits 0 as in 0x0).

<snip>

Using NULL is better style, but an integer constant expression with a
value of 0 as shown by gert is also a valid null pointer constant and
even if null pointers are not all bits zero it will work.
--
Flash Gordon

[Jens Thoms Toerring]

Flash Gordon <sp**@flash-gordon.me.ukwro te:

Jens Thoms Toerring wrote, On 15/07/07 18:20:

gert <ge**********@g mail.comwrote:

<snip>

char **query = {"SHOW DATABASES;", 0x0 };

You should use NULL instead of 0x0 - NULL is null pointer
while 0x0 is an integer constant (and the representation
of a null pointer isn't necessarily all bits 0 as in 0x0).

<snip>

Using NULL is better style, but an integer constant expression with a
value of 0 as shown by gert is also a valid null pointer constant and
even if null pointers are not all bits zero it will work.

Sorry, of course - the 0 is here used where the compiler expects
a pointer, so it will automagically convert it to a NULL pointer.
I guess my brain is starting to boil after a temperature jump of
15 degree C here within 2 days...
Regards, Jens
--
\ Jens Thoms Toerring ___ [e-mail]
\______________ ____________ http://toerring.de