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 55726 - Passing unknown value to CORBA_ORB_resolve_initial_references (XXX, say), and then RootPOA segfaults in ORBit
Passing unknown value to CORBA_ORB_resolve_initial_references (XXX, say), and...
Status: RESOLVED FIXED
Product: ORBit
Classification: Deprecated
Component: general
0.5
Other Linux
: Normal major
: ---
Assigned To: ORBit maintainers
ORBit maintainers
: 56111 60992 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-06-04 22:38 UTC by Jason Tackaberry
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jason Tackaberry 2001-06-04 22:38:10 UTC 
With ORBit 0.5.8, the following code:

    poa = (PortableServer_POA)CORBA_ORB_resolve_initial_references(orb,
"XXX", &ev);
    poa = (PortableServer_POA)CORBA_ORB_resolve_initial_references(orb,
"RootPOA", &ev);

Segfaults with the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
0x4005b7d4 in ORBit_POAManager_unregister_poa (poa_mgr=0x0, poa=0x804d748, 
    ev=0x0) at orbit_poa.c:165
165             poa_mgr->poa_collection =
g_slist_remove(poa_mgr->poa_collection, poa);
(gdb) bt

+ Trace 5892

  • #0 ORBit_POAManager_unregister_poa
    at orbit_poa.c line 165
  • #1 ORBit_POA_release
    at orbit_poa.c line 342
  • #2 ORBit_POA_new
    at orbit_poa.c line 322
  • #3 CORBA_ORB_resolve_initial_references
    at orb.c line 1045
  • #4 main 






Comment 1


Elliot Lee





          2001-09-11 22:02:37 UTC
        



Give it a whirl in CVS.






Comment 2


Ben FrantzDale





          2002-07-31 05:03:57 UTC
        



*** Bug 60992 has been marked as a duplicate of this bug. ***






Comment 3


Ben FrantzDale





          2002-07-31 05:04:56 UTC
        



*** Bug 56111 has been marked as a duplicate of this bug. ***