xffm crash with empty dir
edscott at imp.mx
Wed May 14 20:27:11 CEST 2003
On Wed, 2003-05-14 at 12:49, Jasper Huijsmans wrote:
> On Wed, 14 May 2003 14:53:25 +0200
> Jasper Huijsmans <jasper at moongroup.com> wrote:
> > edscott,
> > this crash is repeatable for me:
> > 1) open a directory containing only one item
> > 2) trash the last item => xffm shows empty row
> > 3) dnd copy something => sometimes crash, sometimes it's copied, but
> > xffm still shows empty row above new item
> > 4) double click on empty row => crash
I'm checking it on FreeBSD, where instead of a crash, xffm goes off into
an infinite loop at 100% CPU. (I started upgrading my box at work from
RH-8.0 to RH-9.0 and ended with FreeBSD-4.8).
> > I have the local waste baskets hidden. It doesn't happen if I show
> > them(there is no empty row then).
I found another with wastebaskets hidden: close the test directory and
you lose the expander and can no longer open the directory (until
wastebaskets are unhidden or something added to the directory).
> without the copy (just double-click on empty row):
> ** ERROR **: file goto.c: line 124 (pushgo): should not be reached
> xffm: signal 6 received. Cleaning up before exiting
Good: a g_assert_not_reached(). I see what's wrong.
> with dnd copy over empty row:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 21726)]
> 0x407ccf93 in strlen () from /lib/libc.so.6
> (gdb) bt
> #0 0x407ccf93 in strlen () from /lib/libc.so.6
> #1 0x40037c8e in abreviate () from /usr/lib/libxffm.so.0
> #2 0x0000000a in ?? ()
Aja! It must be a something printing to the diagnostic window or status
I'll fix these as soon as I get home.
> Hope this helps,
Very much indeed.
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
edscott <edscott at imp.mx>
More information about the Xfce4-dev