[gutsy] Anjuta crash when call "help display"

[Jorge Pereira]

Binary package hint: anjuta

Steps to reproduce:
1. Open anjuta
2. Click on "help display"
3. this app crash

Stack trace:
[New Thread -1294550128 (LWP 8310)]
[New Thread -1302942832 (LWP 8311)]
[Thread -1294550128 (LWP 8310) exited]
[Thread -1302942832 (LWP 8311) exited]

thread apply all bt

Program received signal SIGINT, Interrupt.
[Switching to Thread -1227278672 (LWP 8303)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 1 (Thread -1227278672 (LWP 8303)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb727c647 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb739e593 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x089c1700 in ?? ()
#4 0x0000000a in ?? ()
#5 0x00000063 in ?? ()
#6 0x089c1700 in ?? ()
#7 0x0000000a in ?? ()
#8 0xb742821c in ?? () from /usr/lib/libglib-2.0.so.0
#9 0xb7304541 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#10 0xb739e909 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#11 0xb79d49e4 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x0805413d in main (argc=Cannot access memory at address 0xa
) at main.c:393
#13 0xb71c9050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#14 0x0804e101 in _start ()
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0xb34d7090 in ?? () from /usr/lib/firefox/libgtkembedmoz.so
(gdb)
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.

Other information:
Ubuntu Linux 7.10

$ uname -a
Linux jaspion 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
$

[Jorge Pereira (jpereiran)]

But, i try fix this problem, i found this problem.

# ldd /usr/lib/firefox/libgtkembedmoz.so | grep "not"
        libxpcom.so => not found
        libxpcom_core.so => not found
#

above folowing my solution in "ubuntu 7.10"

# echo "/usr/lib/firefox/" > /etc/ld.so.conf.d/firefox.conf
# ldconfig

and re-open anjuta app, and resolv this problem.

[Sergey Dudanov (dudanov)]

Same problem! Your solution help me, thanks!

[Sebastien Bacher (seb128)]

could you try if that's still an issue in hardy?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.