Re: [Nautilus-list] nautilus crash while editing files with gedit

[Louis Garcia <louisg00 bellsouth net>]

The new and improved trace:
-------------------------------------------------------
Script started on Wed Nov 28 22:47:23 2001
# nautilus --quit
# MALLOC_CHECK_=2 gdb nautilus
GNU gdb Red Hat Linux 7.x (5.0rh-15) (MI_OUT)
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux"...
(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/nautilus
[New Thread 1024 (LWP 5010)]
[New Thread 2049 (LWP 5022)]
[New Thread 1026 (LWP 5023)]
[New Thread 2051 (LWP 5024)]
[New Thread 3076 (LWP 5045)]
[New Thread 4101 (LWP 5046)]
[New Thread 5126 (LWP 5047)]

Program received signal SIGABRT, Aborted.
[Switching to Thread 1024 (LWP 5010)]
0x40992ae1 in __kill () from /lib/i686/libc.so.6
(gdb) bt
#0  0x40992ae1 in __kill () from /lib/i686/libc.so.6
#1  0x408a876b in raise (sig=6) at signals.c:65
#2  0x40994062 in abort () at ../sysdeps/generic/abort.c:88
#3  0x409e6f57 in free_check () at malloc.c:4668
#4  0x409e4c4d in __libc_free (mem=0x83598d8) at malloc.c:3122
#5  0x408df9f2 in g_free () from /usr/lib/libglib-1.2.so.0
#6  0x40069a58 in top_left_read_callback (result=GNOME_VFS_OK,
    bytes_read=6373,
    file_contents=0x83f4c00 "echo \"removing unwanted
packages...\"\n\nrpm -e XFree86-tools\nrpm -e XFree86-twm\nrpm -e
XFree86-xdm\nrpm -e XFree86-ISO8859-15-75dpi-fonts\nrpm -e
XFree86-ISO8859-15-100dpi-fonts\nrpm -e apmd\nrpm -e autofs\n"...,
callback_data=0x835b588) at nautilus-directory-async.c:2474
#7  0x4041cb32 in read_file_succeeded () from /usr/lib/libeel.so.0
#8  0x40b5a56b in dispatch_read_callback ()
   from /usr/lib/libgnomevfs-pthread.so
#9  0x40b5abcb in dispatch_job_callback () from
/usr/lib/libgnomevfs-pthread.so
#10 0x408df79d in g_idle_dispatch () from /usr/lib/libglib-1.2.so.0
#11 0x408de773 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0
#12 0x408ded39 in g_main_iterate () from /usr/lib/libglib-1.2.so.0
#13 0x408deeec in g_main_run () from /usr/lib/libglib-1.2.so.0
#14 0x407cf333 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#15 0x401771ec in bonobo_main () at eval.c:41
#16 0x080714d1 in main () at eval.c:41
---Type <return> to continue, or q <return> to quit---
#17 0x40980627 in __libc_start_main (main=0x8070fb0 <main>, argc=1,
    ubp_av=0xbffffa84, init=0x805f410 <_init>, fini=0x80b4850 <_fini>,
    rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffffa7c)
    at ../sysdeps/generic/libc-start.c:129
(gdb) quit
The program is running.  Exit anyway? (y or n) y
# exit

Script done on Wed Nov 28 22:51:21 2001
-----------------------------------------------------------------

For your enjoyment. I will file a bug report in the morning.

Louis


On Wed, 2001-11-28 at 22:34, Havoc Pennington wrote:
> 
> Louis Garcia <louisg00 bellsouth net> writes:
> > Ok, This is my first time doing a back trace, be gentile.
> >
> 
> The trace is good, but its specific content indicates that it would be
> worth re-doing the trace like this:
> 
> $ MALLOC_CHECK_=2 gdb nautilus
> 
> Since it appears to be a double-free or other memory corruption, this
> may reveal a more accurate trace. Or may not, it might crash in the
> same place.
>  
> Havoc