Re: [g-a-devel] Problem with fatal critical warnings and a11y

[Kjartan Maraas <kmaraas broadpark no>]

man, 09,.01.2006 kl. 10.39 +0000, skrev Bill Haneman:
> Hi Kjartan:
> 
> As far as I can see, the assertions are appropriate.  So, do you have a 
> stack trace showing who/what is passing bum data to 
> spi_accessible_construct?
> 

This is the backtrace I saw from valgrind:

==14948== Process terminating with default action of signal 4 (SIGILL)
==14948==  Illegal opcode at address 0x4B543A8
==14948==    at 0x4B543A8: g_logv (gmessages.c:493)
==14948==    by 0x4B54427: g_log (gmessages.c:517)
==14948==    by 0x4B544E4: g_assert_warning (gmessages.c:552)
==14948==    by 0x50AF398: spi_accessible_construct (accessible.c:495)
==14948==    by 0x50B05E2: spi_application_new (application.c:292)
==14948==    by 0x50DC257: atk_bridge_init (bridge.c:180)
==14948==    by 0x50DCE02: gnome_accessibility_module_init (bridge.c:533)
==14948==    by 0x418547B: accessibility_invoke_module (gnome-program.c:1601)
==14948==    by 0x4185583: accessibility_invoke (gnome-program.c:1632)
==14948==    by 0x41856C1: accessibility_init (gnome-program.c:1673)
==14948==    by 0x41857D4: gnome_program_postinit (gnome-program.c:1713)
==14948==    by 0x4185C6E: gnome_program_init_common (gnome-program.c:1928)
==14948==    by 0x4185CA6: gnome_program_initv (gnome-program.c:1965)
==14948==    by 0x4185828: gnome_program_init (gnome-program.c:1746)
==14948==    by 0x8053806: main (main.c:398)

Cheers
Kjartan