cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
457 Views
Registered: ‎04-24-2020

Simulator: Abnormal program termination (11)

I'm running Vivado 2020.1 on Ubuntu 20.04.  I get crashes in the simulator when pressing the toolbar "Run (T)" button, the button for running the simulation for the specified amount of time.  The majority of times it works OK, but every once in a while, the application suddenly dies and I see the following in my Terminal:

Abnormal program termination (11)
Please check '..../behav/xsim/hs_err_pid15364.log' for details
segfault in /opt/Xilinx/Vivado/2020.1/bin/unwrapped/lnx64.o/vivado -exec vivado, exiting...

Any help with this would be much appreciated.  It is just a minor annoyance at the moment, since I can restart the simulator and it will continue to work for a while, before crashing again.  However it does impact productivity somewhat.

The log has the following contents:

#
# An unexpected error has occurred (11)
#
Stack:
/opt/Xilinx/Vivado/2020.1/tps/lnx64/jre9.0.4/lib//server/libjvm.so(+0xb6aadb) [0x7faa25105adb]
/opt/Xilinx/Vivado/2020.1/tps/lnx64/jre9.0.4/lib//server/libjvm.so(JVM_handle_linux_signal+0xbb) [0x7faa2510ae1b]
/opt/Xilinx/Vivado/2020.1/tps/lnx64/jre9.0.4/lib//server/libjvm.so(+0xb647b8) [0x7faa250ff7b8]
/lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7faa74ad2210]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::CArray::empty() const+0) [0x7faa2b8f3a00]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbEventBlock::addBlock(SimBridge::WdbIBlockManager&, unsigned int&) const+0x1c) [0x7faa2b8f40dc]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbMultipleBucketEventDatabase::getEventBlockDatabaseIterator(std::vector<SimBridge::WdbScalarBTree*, std::allocator<SimBridge::WdbScalarBTree*> > const&, std::vector<boost::shared_ptr<SimBridge::WdbIEventBlockIterator>, std::allocator<boost::shared_ptr<SimBridge::WdbIEventBlockIterator> > >&, std::vector<std::vector<SimBridge::WdbScalarBTree*, std::allocator<SimBridge::WdbScalarBTree*> >, std::allocator<std::vector<SimBridge::WdbScalarBTree*, std::allocator<SimBridge::WdbScalarBTree*> > > >&) const+0x691) [0x7faa2b90e071]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbAddressBTreeManager::scanWdbDatabaseMultiThread(std::vector<SimBridge::WdbScalarBTree*, std::allocator<SimBridge::WdbScalarBTree*> > const&, ISIM::IGuiStatus*)+0xf0) [0x7faa2b8eaee0]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(SimBridge::DataObjMgr::createDrawingBTree(std::vector<SimBridge::IDataObj const*, std::allocator<SimBridge::IDataObj const*> > const&, ISIM::IGuiStatus*, bool)+0x32a) [0x7faa355ca83a]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(SimBridge::DataReader::getTransitions(SimBridge::IDataObj const*, long long, long long, long long, SimBridge::ValueFormat const&, std::vector<SimBridge::Transition, std::allocator<SimBridge::Transition> >&) const+0x75) [0x7faa355d5ed5]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(SG_Model::ModelImp::getTransitions(SimBridge::IDataObj const*, SG_Model::IDatabase*, long long, long long, long long, SimBridge::ValueFormat const&, bool, std::vector<SimBridge::Transition, std::allocator<SimBridge::Transition> >&) const+0xbd) [0x7faa3567c44d]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(SG_Model::Model::getTransitions(SG_Model::WVDataObject const*, long long, long long, long long, SimBridge::ValueFormat const&, bool, std::vector<SimBridge::Transition, std::allocator<SimBridge::Transition> >&) const+0x102) [0x7faa3567c7d2]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(+0x3031d2) [0x7faa356ae1d2]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(SG_Model::WaveformRender::render(SG_Model::WVDataObject const&)+0x2ac) [0x7faa356aa92c]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WaveViewer::WVWaveformPanel::WaveformTraverser::drawWaveform(SG_Model::WVDataObject const*, int, int)+0x2eb) [0x7faa357275eb]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WaveViewer::WVWaveformPanel::WaveformTraverser::handleItemSize(WaveViewer::WVNameValueTreeModel::ITraverseHandler::ItemSize const&)+0x4a) [0x7faa357278ca]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WaveViewer::WVNameValueTreeModel::traverseYRange(SG_Model::WVDataObject const*, WaveViewer::WVNameValueTreeModel::ITraverseHandler&, int, int, int&, int&) const+0x268) [0x7faa356f9958]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WaveViewer::WVNameValueTreeModel::traverseYRange(SG_Model::WVDataObject const*, WaveViewer::WVNameValueTreeModel::ITraverseHandler&, int, int, int&, int&) const+0x336) [0x7faa356f9a26]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WaveViewer::WVNameValueTreeModel::traverseYRange(WaveViewer::WVNameValueTreeModel::ITraverseHandler&, int, int) const+0x57) [0x7faa356faa37]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WaveViewer::WVWaveformPanel::getGraphics(HDGDStringStream&, long&)+0x3c5) [0x7faa35726ae5]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WVExecutiveImp::getGraphicsDataSize()+0x10a) [0x7faa356eaf8a]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(WVExecutive::getGraphicsDataSize()+0xf) [0x7faa356eb4af]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_wavedata.so(Java_ui_views_waveform_waveformi_WVExecutive_1getGraphicsDataSize+0x17) [0x7faa35731da7]
[0x7faa1622b191]

0 Kudos
7 Replies
Highlighted
Xilinx Employee
Xilinx Employee
382 Views
Registered: ‎09-05-2018

Hi @ElementGreen ,

Vivado is not supported on Ubuntu 20.04 OS version. Please have a look into below link ( Page no-8 ) for the list of supported OS.

https://www.xilinx.com/support/documentation/sw_manuals/xilinx2020_1/ug973-vivado-release-notes-install-license.pdf

Regards,

Saketh

0 Kudos
Highlighted
Visitor
Visitor
361 Views
Registered: ‎04-24-2020

Yes, I realize this and understand that Xilinx doesn't provide support for this distribution of Linux.  However, despite the fact it isn't officially supported on Ubuntu, I've been using ISE and Vivado for years with several versions of it.  I posted this mainly to see if anyone else in the wider community is having the same issue or has any idea of what I might be able to do to resolve it, since I suspect many other users are also using Ubuntu (or other "fringe" unsupported versions of Linux).  Other than this one problem, Vivado 2020.1 has been working great.

Thank you for mentioning this and rest assured, I'm not expecting any official Xilinx support for this issue.

Best regards,

Element Green

0 Kudos
Highlighted
Newbie
Newbie
294 Views
Registered: ‎08-14-2020

I get a similar problem unter Ubun tu 18.04 and Viviado 2020.1:

On the terminal I see:

start_gui
shm_open: No such file or directory
Abnormal program termination (11)
Please check '/media/psf/TX-VA/fpga/ctrl/ctrl.sim/ctrl_top_tb/behav/xsim/hs_err_pid2327.log' for details
segfault in /opt/Xilinx/Vivado/2020.1/bin/unwrapped/lnx64.o/vivado -exec vivado, exiting...

The log file states:

#
# An unexpected error has occurred (11)
#
Stack:
/opt/Xilinx/Vivado/2020.1/tps/lnx64/jre9.0.4/lib//server/libjvm.so(+0xb6aadb) [0x7f139a898adb]
/opt/Xilinx/Vivado/2020.1/tps/lnx64/jre9.0.4/lib//server/libjvm.so(JVM_handle_linux_signal+0xbb) [0x7f139a89de1b]
/opt/Xilinx/Vivado/2020.1/tps/lnx64/jre9.0.4/lib//server/libjvm.so(+0xb647b8) [0x7f139a8927b8]
/lib/x86_64-linux-gnu/libc.so.6(+0x3efd0) [0x7f13ebe18fd0]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbCircularBuffer::canRead(unsigned int&, unsigned int&, unsigned int&) const+0x4) [0x7f13a127fd14]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbCircularBuffer::getPackets(void*, unsigned int&)+0x37) [0x7f13a127fe37]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbSharedMemMgr::getPackets(char*, unsigned int&)+0x35) [0x7f13a12a3da5]
/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/librdi_simbridge_kernel.so(SimBridge::WdbSharedMemReader::runReadThread(SimBridge::WdbIEventBlockDatabase*)+0x5a) [0x7f13a12a5d9a]

/opt/Xilinx/Vivado/2020.1/lib/lnx64.o/libboost_thread.so(+0xfa0d) [0x7f13ea29aa0d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f13ebbc26db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f13ebefba3f]

Any suggestion how this can be resolved and/or where I can get more information?

Best regards, a.

0 Kudos
Highlighted
Visitor
Visitor
277 Views
Registered: ‎04-24-2020

This doesn't seem related to the issue I have been having.  The issue I described occurs during simulation occasionally when reloading or running it. Seems the problem you described occurs when you try and start vivado?  Looking at the error message "shm_open: No such file or directory" and the backtrace seems to indicate something wrong with a shm_open() call, which is used to access system memory between processes.  This suggests the other process which would have created the shared memory segment is not running or there is some other issue preventing it from accessing it.  I think if I was experiencing the same thing as you are, I'd try upgrading my Ubuntu version or testing it on another Ubuntu system (the same version and/or newer) to see if it behaves differently.

I would also check that you are starting Vivado correctly.  In my case I added the Vivado bin directory to my shell's PATH variable in my ~/.bashrc file like so:

export PATH=$PATH:/opt/Xilinx/Vivado/2020.1/bin

Which then makes it to where I can just run "vivado" from the command line.

Best of luck to you.

0 Kudos
Highlighted
Newbie
Newbie
268 Views
Registered: ‎08-14-2020

Yes, you are right. The root cause was that my simulation directory is located on a shared drive which does not support special files. Mounting the remote file system as SSHFS with support for special files solved my specific problem.

Thanks for the hint with "shm_open"!

0 Kudos
Highlighted
Newbie
Newbie
177 Views
Registered: ‎08-14-2020

Just found an even more attractive solution to my specific problem: run vivado with the -tempDir option pointing to a local drive.

0 Kudos
Highlighted
Visitor
Visitor
121 Views
Registered: ‎04-24-2020

Glad you resolved the issue you were having.

Interestingly, I have not experienced the original problem I described in this post since I posted it.  Despite doing a bit of simulation work.  I think it would be wishful thinking to say it is fixed, since I really don't see what I did to resolve the problem.  At least it doesn't occur often though.

0 Kudos