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
but the inner loop for diving thru the $PATH directories for executable
files are SAME as that in dmenu-3.0 - only code that wasn't changed while
adding caching :)
Frank, can you run 'sh -x dmenu_path_from_dmenu3.0' as first place where it
can segfault is: ' test -x "$file" && echo "${file##*/}"'.
--anydot
