El día Wednesday, May 04, 2011 a las 11:48:05AM +0100, David Woodhouse escribió:
> On Wed, 2011-05-04 at 12:45 +0200, Matthias Apitz wrote: > > > 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 ... > > The other thing to try is valgrind. > > Run in valgrind with GSLICE=always-malloc and that may catch some > use-after-free and other memory corruptions which could be causing this. valgrind itself crashes with sig11; I think g_hash_table_new() is not causing this problem; see the addr of e2k_ascii_strcase_hash() which read_config() hands over to it; it's exactly the broken one 0x29ed1f6b and set into the hash_table: Server is up and running... DEBUG e2k-autoconfig: entered read_config() DEBUG e2k-autoconfig: entering now g_hash_table_new(e2k_ascii_strcase_hash, e2k_ascii_strcase_equal): 29ed1f6b, 29ed1f39 DEBUG e2k-autoconfig: right after g_hash_table_new() DEBUG e2k-autoconfig: read_config() config_options=2995efb0: 00000008 00000007 00000007 00000000 00000000 2a57f280 29ed1f6b 29ed1f39 DEBUG e2k-autoconfig: read_config() return, fd=-1 DEBUG e2k-autoconfig: read_config() config_options=2995efb0: 00000008 00000007 00000007 00000000 00000000 2a57f280 29ed1f6b 29ed1f39 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 29804300 (LWP 100272/initial thread)] 0x29ed1f6b in ?? () (gdb) p *0x29ed1f6b Error accessing memory address 0x29ed1f6b: Dirección incorrecta. (gdb) -- 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
