bug in emelfm
Hello,
I have found a strange behaviour in last stable emelfm debian packet, but
I think this a emelfm problem. If I add in file type a new extension ,for
example deb, and I use the name ,for example, View contents and in
command I write "dpkg --contents %f | more" the application goes in crash
in following situation : I have to choose the option "show output
area" and a big packet deb( 4-5 megabyte) ,clicking on "View contents"
the application doesn't answer to the commands and I can't close it
I have to kill the application In gdb I see this:
(gdb) r
Starting program: /usr/X11R6/bin/emelfm
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread
16384 (LWP 1154)]
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New (LWP
1165)]
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 16384 (LWP 1154)]
0x003d889b in write () from /lib/libpthread.so.0
Using command "su dpkg --contents %f | less" is all ok.
Best Regards
Cecco
Reply to: