El día Wednesday, May 04, 2011 a las 10:52:03AM +0100, David Woodhouse escribió:
> On Wed, 2011-05-04 at 11:44 +0200, Matthias Apitz wrote:
> > I have inserted some fprintf's in read_conf() to print in hex the memory
> > of the hash_table (see below); it matches what gdb reads about the
> > hash_table (values marked with ^^^);
>
> Was that *right* after the g_hash_table_new() call?
No, but now I added additional prints right after the call of
g_hash_table_new(), it is not buggered in read_conf():
Server is up and running...
DEBUG e2k-autoconfig: entered read_config()
DEBUG e2k-autoconfig: right after g_hash_table_new()
DEBUG e2k-autoconfig: read_config() config_options=2995dd50:
00000008 00000007 00000007 00000000 00000000 2995f5e0 29ed1f3b 29ed1f09
DEBUG e2k-autoconfig: read_config() return, fd=-1
DEBUG e2k-autoconfig: read_config() config_options=2995dd50:
00000008 00000007 00000007 00000000 00000000 2995f5e0 29ed1f3b 29ed1f09
> That would seem to imply that your hash table was buggered from the very
> beginning. If you really can't get gdb to work properly and use a
> hardware watchpoint, try littering similar printfs all the way through
> g_hash_table_new() so you can find out why it isn't being set to the
> function you *provided*.
will do ...
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <g...@unixarea.de> - w http://www.unixarea.de/
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list
