Hello, I am creating this forum post because I can't seem to find a place to submit a bug report to Intel. I hope that this will help anyone else who runs into the same problem.
The debugger that comes with intel studio 2016 has an error in the debuggervars.sh script found in
/opt/intel/debugger_2016/bin/debuggervars.sh
By default, Ubuntu leaves the MANPATH and INFOPATH shell variables empty. However, setting them overwrites the man and info search paths. To retain the default search paths, ensure an empty string is one of the paths set in MANPATH. I.e.,
export INFOPATH=$GDBMAN
should be
export INFOPATH=$GDBMAN:$INFOPATH
If INFOPATH isn't set, the latter will still work as desired while the former won't. This is an error on lines 97 and 104 of the script.
As a workaround, you can simply add
export MANPATH=${MANPATH}: export INFOPATH=${INFOPATH}:
somewhere in your profile.
链接已复制
Hello,
FYI, we have an article about that problem:
https://software.intel.com/en-us/articles/intel-parallel-studio-xe-2016-for-linux-compilervars-set-manpath-incorrect
Our debugger engineers have fixed that last week and it will be available with update 1.
I'm double checking whether they also addressed $INFOPATH, just to be sure.
Thanks for reporting!
Georg Zitzlsberger
P.S.: I don't see a problem with $INFOPATH because it's already tested for being empty. The only problem with $MATHPATH is that the system configuration (by /usr/bin/manpath) is not handled. If $MANPATH is empty some (not all) distributions use the output of /usr/bin/manpath instead. The solution on our end is to add that output too, once we modify $MANPATH. So, the solution would be something like that:
if [ -z "${MANPATH}" ]
then
export MANPATH=$GDBMAN:`manpath`
else
export MANPATH=$GDBMAN:$MANPATH
fi
