Re: possible bug

[Harring Figueiredo <harringf yahoo com>]

 If you post your coded snipet it would help us find the problem.

 What do you mean by initializing ?

 foo(){
 gchar*  c =  "something" ;
}

  foo(){
  gchar* c = strdup("something");

}

 Both initialize, but have different memory context.

 Again, posting the code would help.

Harring.
--- Jeffrey Goddard <moosewood@mooseroot.org> wrote:
> ok folks,
> i've been around and around with this bug, and this is what i've found thus 
> far. if i have a "gchar *some_variable" which is initialized in a function 
> that is not a callback function, it does not survive going into and out of 
> gtk_main(). upon return from the gtk_main() loop the address is the same as 
> upon entry, but the character string is, generally, the null string. a few, 
> (approx 5%) of the times, it's been an unititialized string. i changed my 
> code so that the strings were initialized within a callback function, and 
> they persist forever. i would like to know why this behaviour is exhibited. 
> i've chased through the documentation, but find no mention of anomolous 
> behaviour in the assignment of character strings to a gchar variable. i would
> 
> love to know what i am missing, or if i've actually stumbled across a bug.(in
> 
> something other than my code).
> Many thanks for any info,
> Jeffrey
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com