启动Vivado v2015.2（64位）时出现分段错误

你好@ polaris042
我仍然观察到设置了环境变量GNOME_DESKTOP_SESSION_ID。
你可以尝试取消它吗？
谢谢，
维奈
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。
在原帖中查看解决方案



以下为原文

Hi @polaris042
 
I still observe that the environmental variable GNOME_DESKTOP_SESSION_ID is set. Can you try unsetting it?
 
Thanks,
Vinay
--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.View solution in original post

你好@ polaris042
取消设置环境变量GNOME_DESKTOP_SESSION_ID并尝试？
谢谢，
维奈
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi @polaris042
 
unset the environmental variable GNOME_DESKTOP_SESSION_ID and try?
 
Thanks,
Vinay
--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

是的，我尝试过但是没有用。
嗯..'unset GNOME_DESKTOP_SESSION_ID'之后的结果是什么？
当我在那之后尝试'echo $ GNOME_DESKTOP_SESSION_ID'时，我得到了'这是被贬低'。
这是正确的结果吗？
谢谢，
Chorong Kim



以下为原文

Yes, I tried it but it doesn't worked.  
 
Hmm.. what is the result after 'unset GNOME_DESKTOP_SESSION_ID' ? 
When I tried 'echo $GNOME_DESKTOP_SESSION_ID' after that, I got 'this-is-depreated'. 
Is it a correct result?
 
Thanks,
Chorong Kim
 

你好@ polaris042
共享命令的输出：env
谢谢，
维奈
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi @polaris042
 
Share the output of the command: env
 
Thanks,
Vinay
--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

您可以使用当前项目的新项目打开。
当前项目可能是此问题的根本原因
谢谢和RegardsBalkrishan -----------------------------------------------
---------------------------------------------请将帖子标记为
一个答案“接受为解决方案”，以防它有助于解决您的查询。如果一个帖子引导到解决方案，请给予赞誉。



以下为原文

You may open with new project inplace of current project.
The current project may be the root cause of this issueThanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

我创建了一个新用户帐户并重试，但报告的错误相同。
我附上了env.log文件。
请检查一下。
谢谢，
Chorong Kim
env.log 5 KB



以下为原文

 
I make a new user account and try again, but the same error is reported. 
I attatched env.log file. Please, check it. 
 
Thanks,
Chorong Kim
            env.log ‏5 KB

返回的是：
ldd /opt/Xilinx/Vivado/2015.2/bin/unwrapped/lnx64.o/vivado
查看2015.2 / lib / lnx64.0 /目录下是否有“未找到”库。
丹尼尔



以下为原文

What is returned by:
 
ldd /opt/Xilinx/Vivado/2015.2/bin/unwrapped/lnx64.o/vivado
 
See if any "not found" libraries are available under the 2015.2/lib/lnx64.0/ directory.
 
Daniel
 

我收到了以下报告。
linux-vdso.so.1 =>（0x00007ffec71cf000）libtcmalloc.so.4 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libtcmalloc.so.4(0x00007fe6afb02000)libboost_signals.so => / opt /
Xilinx / Vivado / 2015.2 / lib / lnx64.o / libboost_signals.so(0x00007fe6af8eb000)librdi_common.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_common.so(0x00007fe6aed38000)librdi_commonmain.so => /
opt / Xilinx / Vivado / 2015.2 / lib / lnx64.o / librdi_commonmain.so(0x00007fe6aeb2c000)libstdc ++。so.6 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libstdc++.so.6(0x00007fe6ae829000）
libgcc_s.so.1 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libgcc_s.so.1(0x00007fe6ae613000)libc.so.6 => /lib64/libc.so.6(0x00007fe6ae23f000)libm。
so.6 => /lib64/libm.so.6(0x00007fe6adf3c000)libpthread.so.0 => /lib64/libpthread.so.0(0x00007fe6add20000)libCOIN-all.so => /opt/Xilinx/Vivado/2015.2/
lib / lnx64.o / libCOIN-all.so(0x00007fe6ad650000)libXil_lmgr11.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libXil_lmgr11.so(0x00007fe6ad2e8000)libboost_date_time.so => / o
pt / Xilinx / Vivado / 2015.2 / lib / lnx64.o / libboost_date_time.so(0x00007fe6ad0d8000)libboost_filesystem.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_filesystem.so(0x00007fe6acec2000)libboost_program_options.so =
> /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_program_options.so(0x00007fe6acc52000)libboost_regex.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_regex.so(0x00007fe6ac96c000)libboost_system。
so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_system.so(0x00007fe6ac769000)libboost_thread.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_thread.so(0x00007fe6ac549000）
libhdlpsolve.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libhdlpsolve.so(0x00007fe6ac2a6000)libhdxml.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libhdxml.so(
0x00007fe6abffc000）libisl_iostreams.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libisl_iostreams.so(0x00007fe6ab7c3000)libisl_iosutils.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libisl_iosutils。
so（0x00007fe6ab5aa000）libisl_sysinfo。
so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libisl_sysinfo.so(0x00007fe6ab377000)libprotobuf.so.7 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libprotobuf.so。
7（0x00007fe6ab085000）librdi_commonxillic.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_commonxillic.so(0x00007fe6aae25000)librdi_curl.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/
librdi_curl.so（0x00007fe6aaa16000）librdiconfig.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdiconfig.so(0x00007fe6aa7fd000)librdizlib.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64。
o / librdizlib.so（0x00007fe6aa5d7000）libtcl8.5.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libtcl8.5.so(0x00007fe6aa2b5000)libxerces-c-3.1.so => / opt /
Xilinx / Vivado / 2015.2 / lib / lnx64.o / libxerces-c-3.1.so(0x00007fe6a9d0a000)libdl.so.2 => /lib64/libdl.so.2(0x00007fe6a9b06000)libgomp.so.1 => / opt /
Xilinx / Vivado / 2015.2 / lib / lnx64.o / libgomp.so.1(0x00007fe6a98f8000)librdi_commonversion.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_commonversion.so(0x00007fe6a96f4000
）/lib64/ld-linux-x86-64.so.2(0x00007fe6afd75000)librt.so.1 => /lib64/librt.so.1(0x00007fe6a94ec000)libboost_iostreams.so => /opt/Xilinx/Vivado/2015.2/
lib / lnx64.o / libboost_iostreams.so（0x00007fe6a92d8000）



以下为原文

 
I got the following report.
 
linux-vdso.so.1 => (0x00007ffec71cf000)
libtcmalloc.so.4 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libtcmalloc.so.4 (0x00007fe6afb02000)
libboost_signals.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_signals.so (0x00007fe6af8eb000)
librdi_common.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_common.so (0x00007fe6aed38000)
librdi_commonmain.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_commonmain.so (0x00007fe6aeb2c000)
libstdc++.so.6 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libstdc++.so.6 (0x00007fe6ae829000)
libgcc_s.so.1 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libgcc_s.so.1 (0x00007fe6ae613000)
libc.so.6 => /lib64/libc.so.6 (0x00007fe6ae23f000)
libm.so.6 => /lib64/libm.so.6 (0x00007fe6adf3c000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fe6add20000)
libCOIN-all.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libCOIN-all.so (0x00007fe6ad650000)
libXil_lmgr11.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libXil_lmgr11.so (0x00007fe6ad2e8000)
libboost_date_time.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_date_time.so (0x00007fe6ad0d8000)
libboost_filesystem.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_filesystem.so (0x00007fe6acec2000)
libboost_program_options.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_program_options.so (0x00007fe6acc52000)
libboost_regex.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_regex.so (0x00007fe6ac96c000)
libboost_system.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_system.so (0x00007fe6ac769000)
libboost_thread.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_thread.so (0x00007fe6ac549000)
libhdlpsolve.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libhdlpsolve.so (0x00007fe6ac2a6000)
libhdxml.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libhdxml.so (0x00007fe6abffc000)
libisl_iostreams.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libisl_iostreams.so (0x00007fe6ab7c3000)
libisl_iosutils.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libisl_iosutils.so (0x00007fe6ab5aa000)
libisl_sysinfo.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libisl_sysinfo.so (0x00007fe6ab377000)
libprotobuf.so.7 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libprotobuf.so.7 (0x00007fe6ab085000)
librdi_commonxillic.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_commonxillic.so (0x00007fe6aae25000)
librdi_curl.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_curl.so (0x00007fe6aaa16000)
librdiconfig.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdiconfig.so (0x00007fe6aa7fd000)
librdizlib.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdizlib.so (0x00007fe6aa5d7000)
libtcl8.5.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libtcl8.5.so (0x00007fe6aa2b5000)
libxerces-c-3.1.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libxerces-c-3.1.so (0x00007fe6a9d0a000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fe6a9b06000)
libgomp.so.1 => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libgomp.so.1 (0x00007fe6a98f8000)
librdi_commonversion.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/librdi_commonversion.so (0x00007fe6a96f4000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe6afd75000)
librt.so.1 => /lib64/librt.so.1 (0x00007fe6a94ec000)
libboost_iostreams.so => /opt/Xilinx/Vivado/2015.2/lib/lnx64.o/libboost_iostreams.so (0x00007fe6a92d8000)
 
 

好吧，它似乎没有丢失任何库。接下来想运行：strace -f vivado -o /tmp/vivado.strace.out这将显示在程序崩溃之前进行的系统调用。



以下为原文

OK, it does not appear you are missing any libraries.

Next thought is to run:

strace -f vivado -o /tmp/vivado.strace.out

That will show you what system calls are made just before the program crashes.

你好@ polaris042
我仍然观察到设置了环境变量GNOME_DESKTOP_SESSION_ID。
你可以尝试取消它吗？
谢谢，
维奈
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi @polaris042
 
I still observe that the environmental variable GNOME_DESKTOP_SESSION_ID is set. Can you try unsetting it?
 
Thanks,
Vinay
--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

有用！
我使用了错误的命令来取消设置GNOME_DESKTOP_SESSION_ID变量。
我应该'unsetenv'命令而不是'unset'因为我使用c-shell环境。
感谢您的支持！
谢谢，
Chorong Kim



以下为原文

 
 
It works! 
 
I used wrong a command for unsetting GNOME_DESKTOP_SESSION_ID variable. 
I should 'unsetenv' command instead of 'unset' because I use c-shell environment. 
Thank you for your supports!
 
 
Thanks, 
Chorong Kim 
 

我偶然发现了这个论坛帖子，其中显示了取消设置环境变量GNOME_DESKTOP_SESSION_ID的解决方法。
我确认此解决方法确实有效，如果将以下命令添加到.bashrc文件中，则每次重新启动计算机时都不需要运行该命令。
取消设置GNOME_DESKTOP_SESSION_ID来自此主题的信息：http：//stackoverflow.com/questions/21261616/ubuntu-13-04-gnome-desktop-session-id如果您在设置Vivado Design Suite时遇到此问题，此线程可以帮助您
2015.2.1在使用CentOS 7的Desktop Linux下（包括1406和1503版本）。
它当然帮助了我！
问候，
-Kevin



以下为原文

I stumbled across this forum post which shows a workaround for unsetting the environment variable GNOME_DESKTOP_SESSION_ID.
 
I confirmed that this workaround indeed does work and if you add the following command to your .bashrc file, you won’t need to run the command each time you restart your machine.  

unset GNOME_DESKTOP_SESSION_ID

That information came from this thread here:

http://stackoverflow.com/questions/21261616/ubuntu-13-04-gnome-desktop-session-id

Hopefully this thread helps if you ever run into this issue while setting up Vivado Design Suite 2015.2.1 under Desktop Linux using CentOS 7 (with both the 1406 and 1503 releases).  It certainly helped me!
 
Regards,
 
-Kevin