On 1/6/06, Egon Kocjan <[EMAIL PROTECTED]> wrote:
Running fish inside of fish is a start, since you can at least see the exit messages then. Even better is to run a valgrind session of fish and write valgrind output to a file. This is only feasible on a really fast computer though, since valgrind really slows things down. Otherwise you can see if running fish in strace or gdb gives you any good information on what goes wrong.
--
Axel
Hi,
Sometimes (once every 3 days) fish crashes, when I tab complete paths for cd
command. Also, I am not 100% sure, maybe its just my konsole from kde 3.5.0,
which is an not-yet-stable preview for upcoming suse 10.1. Anyway, when
problem occurs, konsole simply closes, as if I pressed ^D on an empty line.
So, how do I catch this bug? Run fish inside fish? Run fish in gdb all the
time? :)
Running fish inside of fish is a start, since you can at least see the exit messages then. Even better is to run a valgrind session of fish and write valgrind output to a file. This is only feasible on a really fast computer though, since valgrind really slows things down. Otherwise you can see if running fish in strace or gdb gives you any good information on what goes wrong.
--
Axel
