gcmd-devel
[Top][All Lists]
Advanced

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

[gcmd-dev] Clicking the SMB button causes SIGSEGV in libgnomevfs-2.so.0


From: Manuel Bua
Subject: [gcmd-dev] Clicking the SMB button causes SIGSEGV in libgnomevfs-2.so.0
Date: Fri, 17 Jun 2011 10:34:46 +0200

Hello, i just checkout the master branch and was eager to try out the new
1.4 and i like it pretty much, thank you for your work!
However, trying to browse Samba shares causes gnome-cmd to segfault, here is
the backtrace (w/ full gdb version info):

GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from
/home/xxx/dev/gnome-commander.git/src/.libs/lt-gnome-commander...done.
(gdb) run
Starting program:
/home/xxx/dev/gnome-commander.git/src/.libs/lt-gnome-commander
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe96c1700 (LWP 17494)]

** (lt-gnome-commander:17491): CRITICAL **: void
gnome_cmd_con_ftp_set_host_name(GnomeCmdConFtp*, const gchar*): assertion
`host_name != NULL' failed
[New Thread 0x7fffe315a700 (LWP 17495)]
[Thread 0x7fffe315a700 (LWP 17495) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff610a593 in ?? () from /usr/lib/libgnomevfs-2.so.0
(gdb) bt
#0  0x00007ffff610a593 in ?? () from /usr/lib/libgnomevfs-2.so.0
#1  0x00007ffff6109df3 in gnome_vfs_uri_append_path () from
/usr/lib/libgnomevfs-2.so.0
#2  0x0000000000436815 in smb_create_uri (con=<value optimized out>,
path=0x7cad90) at gnome-cmd-con-smb.cc:145
#3  0x000000000043687a in smb_open (con=0x806920) at gnome-cmd-con-smb.cc:89
#4  0x0000000000437913 in gnome_cmd_con_open (con=0x806920) at
gnome-cmd-con.cc:286
#5  0x00007ffff57a69d8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#6  0x00007ffff2f77a6e in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#7  0x00007ffff2f8dde7 in ?? () from /usr/lib/libgobject-2.0.so.0
#8  0x00007ffff2f8f0eb in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#9  0x00007ffff2f8f863 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#10 0x00007ffff58bf6df in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00007ffff579ee73 in gtk_propagate_event () from
/usr/lib/libgtk-x11-2.0.so.0
#12 0x00007ffff579ff4b in gtk_main_do_event () from
/usr/lib/libgtk-x11-2.0.so.0
#13 0x00007ffff541974c in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#14 0x00007ffff256c342 in g_main_context_dispatch () from
/lib/libglib-2.0.so.0
#15 0x00007ffff25702a8 in ?? () from /lib/libglib-2.0.so.0
#16 0x00007ffff25707b5 in g_main_loop_run () from /lib/libglib-2.0.so.0
#17 0x00007ffff57a03e7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x000000000048d8f5 in main (argc=<value optimized out>, argv=<value
optimized out>) at main.cc:181

I'm using 1.2.8.10 for day-to-day work and this feature obviously works
fine: when testing 1.4 i renamed my previous ".gnome-commander"
configuration store so that i'm sure the problem is not related to
previous/deprecated settings and such.
If you need some more debug information just let me know if there are any
switches i can enable to recompile with more useful dbginfo, i will be happy
to provide them.

-- 
Manuel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]