> Anyway, this is my output:
>
> + CACHE=/home/knarf/.dmenu_cache
> + UPTODATE=1
> + IFS=:
> + test ! -f /home/knarf/.dmenu_cache
> + test 1
> + test /home/knarf/bin -nt /home/knarf/.dmenu_cache
> + test /usr/local/sbin -nt /home/knarf/.dmenu_cache
> + test /usr/local/bin -nt /home/knarf/.dmenu_cache
> + unset UPTODATE
> + test /usr/sbin -nt /home/knarf/.dmenu_cache
> + test /usr/bin -nt /home/knarf/.dmenu_cache
> + unset UPTODATE
> + test /sbin -nt /home/knarf/.dmenu_cache
> + test /bin -nt /home/knarf/.dmenu_cache
> + unset UPTODATE
> + test /usr/games -nt /home/knarf/.dmenu_cache
> + test !
> Segmentation fault
A silly question: can you generate the order in which it queries things without
actually doing the test and see what is being tested when the crash occurs, and
then look to see if it's some strange filesystem object (a socket, dangling
symlink, etc). The fact it's happening at the same place always suggests it's
data dependent. If nothing else, you could move the crashing object temporarily
out of the search path and see if that stops the crash.
cheers, dave tweed
___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
