* Paul Kimoto <[EMAIL PROTECTED]> [070822 01:33]:
> When I run "gv" or "gv SOME_POSTSCRIPT_FILE", it dumps core immediately.
> According to "strace gv", this happens right after
>
> stat64("/home/mopsa/kimoto/.gv", 0xbf9cf394) = -1 ENOENT (No such file or
> directory)
>
> (although "touch ~/.gv" doesn't help).
A backtrace to this would be helpfull.
Could you try to run:
gdb --args gv SOME_POSTSCRIPT_FILE
and then on the prompt
run<RETURN>
waiting for the fault and then
backtrace<RETURN>
and send the output of this?
(Even better would be with a version of gv compiled with debug versions,
and with the debug versions of all libraries installed, but even
without it might give already information what is at fault actually)
Does it happen for all files or only for specific ones?
Does it still happen with an emtpy home directory?
You can try with
mkdir /tmp/test
HOME=/tmp/test gv SOME_POSTSCRIPT_FILE
Is the environment variable XUSERFILESEARCHPATH set?
Thanks in advance,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
