Re: Balsa-2 seg fault



On 2002.07.16 16:30:32 +0100 Peter Bloomfield wrote:
> I'm getting frequent segfaults from the BALSA_2 branch:
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 32760)]
> 0x40b857d3 in ORBit_adaptor_find (orb=0xaaaaaafd, objkey=0x831ddf4)
>     at orbit-adaptor.c:50
> 50		if (adaptorId < 0 || adaptorId >= orb->adaptors->len)
> (gdb) bt
> #0  0x40b857d3 in ORBit_adaptor_find (orb=0xaaaaaafd, objkey=0x831ddf4)
>     at orbit-adaptor.c:50
> #1  0x40b85836 in ORBit_handle_request (orb=0xaaaaaafd, 
> recv_buffer=0x831ddd0)
>     at orbit-adaptor.c:69
> #2  0x40b71e8e in giop_connection_handle_input (lcnx=0x8332cc8)
>     at giop-recv-buffer.c:1110
> #3  0x40baa4b7 in linc_connection_io_handler (gioc=0x0, 
> condition=G_IO_IN,     data=0x8332cc8) at linc-connection.c:841
> #4  0x40babe04 in linc_source_dispatch (source=0x831d2e0,     
> callback=0x40baa44c <linc_connection_io_handler>, user_data=0x8332cc8)
>     at linc-source.c:56
> #5  0x40c09622 in g_main_dispatch (context=0x8119bb8) at gmain.c:1617
> #6  0x40c0a439 in g_main_context_dispatch (context=0x8119bb8) at 
> gmain.c:2161
> #7  0x40c0a7cc in g_main_context_iterate (context=0x8119bb8, block=1,     
> dispatch=1, self=0x8119498) at gmain.c:2242
> #8  0x40c0ae72 in g_main_loop_run (loop=0x825e0e0) at gmain.c:2462
> #9  0x408e6873 in gtk_main () at gtkmain.c:936
> #10 0x0807d390 in main (argc=1, argv=0xbffff7d4) at main.c:440
> #11 0x40cce1c4 in __libc_start_main () from /lib/libc.so.6
> 
> Does anyone else see this, or am I especially lucky?

offhand i'd say this is general gnome2 borkage


-- 
Carlos Morgado - chbm(at)chbm(dot)nu - http://chbm.nu/ -- gpgkey: 0x1FC57F0A
http://wwwkeys.pgp.net/ FP:0A27 35D3 C448 3641 0573 6876 2A37 4BB2 1FC5 7F0A
Software is like sex; it's better when it's free. - Linus Torvalds



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