After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 88403 - Seg fault in ORBit_adaptor_find
Seg fault in ORBit_adaptor_find
Status: VERIFIED INCOMPLETE
Product: ORBit2
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: ORBit maintainers
ORBit maintainers
Depends on:
Blocks:
 
 
Reported: 2002-07-17 00:36 UTC by PeterBloomfield
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description PeterBloomfield 2002-07-17 00:36:49 UTC 
The gtk+-2.0 port of Balsa, an email client, has recently begun
seg-faulting on a regular basis, always in ORBit_adaptor_find:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 25144

Thread 1024 (LWP 21618)

  • #0 ORBit_adaptor_find
    at orbit-adaptor.c line 50
  • #1 ORBit_handle_request
    at orbit-adaptor.c line 69
  • #2 giop_connection_handle_input
    at giop-recv-buffer.c line 1110
  • #3 linc_connection_io_handler
    at linc-connection.c line 841
  • #4 linc_source_dispatch
    at linc-source.c line 56
  • #5 g_main_dispatch
    at gmain.c line 1617
  • #6 g_main_context_dispatch
    at gmain.c line 2161
  • #7 g_main_context_iterate
    at gmain.c line 2242
  • #8 g_main_loop_run
    at gmain.c line 2462
  • #9 gtk_main
    at gtkmain.c line 936
  • #10 main
    at main.c line 440
  • #11 __libc_start_main
    from /lib/libc.so.6
  • #1 ORBit_handle_request
    at orbit-adaptor.c line 69 
orb = 0x83cd438
adaptor = 0x83cd438
objkey = (ORBit_ObjectKey *) 0x83aa984

The stack trace contains no Balsa calls after gtk_main(), and Balsa was
running under `MALLOC_CHECK_=2 gdb src/balsa', so there are no heap
problems from other threads.

Others testing the same cvs code have reported no similar problems, so this
may be caused by some peculiarity of my setup:

$ cvs -z3 status src/orb/poa/orbit-adaptor.c
===================================================================
File: orbit-adaptor.c  	Status: Up-to-date

   Working revision:	1.12
   Repository revision:	1.12	/cvs/gnome/ORBit2/src/orb/poa/orbit-adaptor.c,v
   Sticky Tag:		gnome-2-0-0 (branch: 1.12.6)
   Sticky Date:		(none)
   Sticky Options:	(none)

$ cvs -z3 status src/orb/GIOP/giop-recv-buffer.c
===================================================================
File: giop-recv-buffer.c	Status: Up-to-date

   Working revision:	1.49
   Repository revision:	1.49	/cvs/gnome/ORBit2/src/orb/GIOP/giop-recv-buffer.c,v
   Sticky Tag:		gnome-2-0-0 (branch: 1.49.2)
   Sticky Date:		(none)
   Sticky Options:	(none)
$ cvs -z3 status src/linc-connection.c
===================================================================
File: linc-connection.c	Status: Up-to-date

   Working revision:	1.67
   Repository revision:	1.67	/cvs/gnome/linc/src/linc-connection.c,v
   Sticky Tag:		gnome-2-0-0 (branch: 1.67.2)
   Sticky Date:		(none)
   Sticky Options:	(none)
Comment 1 Michael Meeks 2002-07-24 10:17:46 UTC 
committed a potential fix to HEAD ORBit2 - I'd be interested if it
fixes your problem; Thanks.
Comment 2 PeterBloomfield 2002-07-24 13:19:42 UTC 
Yes! The app has been running for several minutes now; that may not
sound like much, but it's a lot longer than it has been! I'll leave it
running for a day or so and report back.

Thanks,

Peter
Comment 3 PeterBloomfield 2002-07-25 08:38:34 UTC 
The app has now been running for a day with no signs of problems.
Marking the bug closed. Thanks for the fix!