at-spi-registryd crashed with signal 5 in ORBit_marshal_object()

Bug #339426 reported by Meigs
6
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: at-spi

Unsure of cause

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/at-spi/at-spi-registryd
NonfreeKernelModules: nvidia
Package: at-spi 1.25.92-0ubuntu1
ProcCmdline: /usr/lib/at-spi/at-spi-registryd
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: at-spi
StacktraceTop:
 ORBit_marshal_object () from /usr/lib/libORBit-2.so.0
 ORBit_marshal_value () from /usr/lib/libORBit-2.so.0
 ORBit_marshal_arg () from /usr/lib/libORBit-2.so.0
 ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0
 ?? () from /usr/lib/libORBit-2.so.0
Title: at-spi-registryd crashed with signal 5 in ORBit_marshal_object()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Meigs (meigs-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:ORBit_marshal_object (buf=0x9c3d4c0, obj=0x9c499b8)
ORBit_marshal_value (buf=0x9c3d4c0, val=0xbfa6c8a4,
?? () from /usr/lib/libORBit-2.so.0
ORBit_small_invoke_adaptor (adaptor_obj=0x9c39f40,
ORBit_POAObject_handle_request (pobj=0x9c39f40,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in at-spi:
importance: Undecided → Medium
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

I am seeing some scrambled text in the Apport Service retraces, for example:

From the Stacktrace.txt

#7 0xb7e5fcf2 in ORBit_POAObject_invoke_incoming_request (pobj=0x9c39f40,
    recv_buffer=0x9c4d908, opt_ev=0xbfa6cacc) at poa.c:1427
 opname = <value optimized out>
 real_ev = {_id = 0xbfa6caa8 "\b˦¿©þå·@\237Ã\t\bÙÄ\tÌʦ¿ôÏç·\001",
  _major = 0, _any = {_type = 0x1, _value = 0xbfa6cae0, _release = 168 '¨'}}
 ev = (CORBA_Environment *) 0xbfa6cacc

#30 0xb7e5fcf2 in ORBit_POAObject_invoke_incoming_request (pobj=0x9c3d428,
    recv_buffer=0x9c467b0, opt_ev=0xbfa6d17c) at poa.c:1427
 opname = <value optimized out>
 real_ev = {_id = 0xbfa6d158 "¸Ñ¦¿©þå·(ÔÃ\t°gÄ\t|Ѧ¿ôÏç·\001",
  _major = 0, _any = {_type = 0x1, _value = 0xbfa6d190, _release = 88 'X'}}
 ev = (CORBA_Environment *) 0xbfa6d17c

From the StacktraceSource.txt file:

#39 0xb7eb4c83 in bonobo_main () at bonobo-main.c:307
  [Error: bonobo-main.c was not found in source tree]
#40 0x0804fa65 in main (argc=) at registry-main.c:83
  78: {
  79: #ifdef AT_SPI_DEBUG
  80: fprintf (stderr, "SpiRegistry Message: SpiRegistry daemon is running.\n");
  81: #endif
  82: registry_set_ior (registry);
  83: bonobo_main ();
  84: }
  85:
  86: return 0;
  87: }

From the ThreadStacktrace.txt

#7 0xb7e5fcf2 in ORBit_POAObject_invoke_incoming_request (pobj=0x9c39f40,
    recv_buffer=0x9c4d908, opt_ev=0xbfa6cacc) at poa.c:1427
 opname = <value optimized out>
 real_ev = {_id = 0xbfa6caa8 "\b˦¿©þå·@\237Ã\t\bÙÄ\tÌʦ¿ôÏç·\001",
  _major = 0, _any = {_type = 0x1, _value = 0xbfa6cae0, _release = 168 '¨'}}
 ev = (CORBA_Environment *) 0xbfa6cacc

#30 0xb7e5fcf2 in ORBit_POAObject_invoke_incoming_request (pobj=0x9c3d428,
    recv_buffer=0x9c467b0, opt_ev=0xbfa6d17c) at poa.c:1427
 opname = <value optimized out>
 real_ev = {_id = 0xbfa6d158 "¸Ñ¦¿©þå·(ÔÃ\t°gÄ\t|Ѧ¿ôÏç·\001",
  _major = 0, _any = {_type = 0x1, _value = 0xbfa6d190, _release = 88 'X'}}
 ev = (CORBA_Environment *) 0xbfa6d17c

visibility: private → public
Changed in at-spi (Ubuntu):
status: New → Triaged
tags: added: a11y
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.