Re: Help



Here is the stack trace:

#0  0x401ca179 in chunk_alloc () from /lib/libc.so.6
(gdb) bt
#0  0x401ca179 in chunk_alloc () from /lib/libc.so.6
#1  0x401cb32b in calloc () from /lib/libc.so.6
#2  0x400e5adf in g_malloc0 (n_bytes=28) at gmem.c:153
#3  0x400353a6 in ORBit_alloc_by_tc (tc=0x4005b8c0) at
allocators.c:362
#4  0x4002f73f in ORBit_small_alloc (tc=0x21) at
orbit-small.c:44
#5  0x4003cf61 in IOP_ObjectKey_demarshal (buf=0x1c)
at iop-profiles.c:1015
#6  0x4003dc27 in IOP_TAG_INTERNET_IOP_demarshal (p=0,
pbuf=0x21, orb=0x8052ce8) at iop-profiles.c:1569
#7  0x4003dd78 in IOP_profile_demarshal (buf=0x50,
orb=0x1c) at iop-profiles.c:1616
#8  0x4003deb2 in ORBit_demarshal_IOR (orb=0x8052ce8,
buf=0x805e3e8, ret_type_id=0x0,
ret_profiles=0xbffff6b8)
    at iop-profiles.c:1676
#9  0x40032811 in ORBit_handle_location_forward
(buf=0x805e3e8, obj=0x1c) at corba-object.c:350
#10 0x4003016d in orbit_small_demarshal
(obj=0x8053448, cnx=0x504f4947, recv_buffer=0x805e3e8,
ev=0xbffff880, 
    ret=0xbffff834, m_data=0x804b100, args=0xbffff830)
at orbit-small.c:532
#11 0x40030371 in ORBit_small_invoke_stub
(obj=0x8053448, m_data=0x804b100, ret=0xbffff834,
args=0xbffff830, ctx=0x0, 
    ev=0xbffff880) at orbit-small.c:645
#12 0x40030230 in ORBit_small_invoke_stub_n
(object=0x21, methods=0x804b164, index=1347373383,
ret=0x21, args=0x21, 
    ctx=0x21, ev=0x50) at orbit-small.c:571
#13 0x40043a72 in ORBit_c_stub_invoke (obj=0x8053448,
methods=0x21, method_index=33, ret=0xbffff834,
args=0xbffff830, 
    ctx=0x0, ev=0xbffff880, class_id=33,
method_offset=33, 
    skel_impl=0x804b164
<CisFiguration_v0_Figuration__iinterface+4>) at
poa.c:2492
#14 0x08049555 in
CisFiguration_v0_Figuration_figureBlocks
(_obj=0x8053448, blocks=0x805347c, ev=0xbffff880)
    at cisFiguration-stubs.c:13
#15 0x080493c9 in client_run
(figuration_service=0x8053448, ev=0xbffff880) at
testfiguration.c:163
#16 0x080494a9 in main (argc=1, argv=0xbffff944) at
testfiguration.c:190
#17 0x4016d0c4 in __libc_start_main () from
/lib/libc.so.6

--- Michael Meeks <michael@ximian.com> wrote:
> 
> On Fri, 2003-11-14 at 16:54, some one wrote:
> > I'm writing a client appliation using Orbit that
> will
> > talk to a server using IONAs Orbix.  I have an IOR
> > file that I use to connect to the server, but get
> a
> > warning message that indicates:
> > 
> > WARNING **: Ignoring incoming code_sets component.
> > 
> > Can someone tell me what this means and does it
> have
> > anything to do with why my application is coring?
> 
> 	It shouldn't be related. It means we're simply
> ignoring the code-set of
> the incoming strings; we deal with only UTF-8 really
> internally, and I
> don't really want to be getting into the tangled
> mess of other
> code-sets.
> 
> 	To debug your problem we need more data; re-compile
> ORBit2 with
> --enable-debug; then export ORBIT2_DEBUG=all and run
> it again; that
> should give us enough data to get a handle on it. It
> would also help to
> have a stack trace. Run it in gdb, then do 'thread
> apply all backtrace'
> and post the result.
> 
> 	Thanks,
> 
> 		Michael.
> 
> -- 
>  michael@ximian.com  <><, Pseudo Engineer, itinerant
> idiot
> 
> _______________________________________________
> orbit-list mailing list
> orbit-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/orbit-list


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]