[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#767025: Bug : jessie - libc6 xilinx vivado 2014.2 crashes



Package: libc6-amd64
Version: 2.19-11

Architecture: amd64
Multi-Arch: same
Source: glibc
Replaces: libc6-amd64
Provides: glibc-2.19-1

Details to the debian build I am working on
/----
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-no



arch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID:    Debian
Description:    Debian GNU/Linux testing (jessie)
Release:    testing
Codename:    jessie
\----


Kernel Version :
3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux

How to reproduce the bug:
-> Install xilinx Vivado 2014.2 (replace the sh -> dash link to
sh->bash otherwise install script fails)
-> source /<INST_DIR>/Vivado/2014.2/settings64.sh
-> start vivado by :~$ vivado&
-> create some custom design with Zynq (PS) and AXI Interface, FIFO
cores etc. Can provide a
example design if needed...
-> Run synthesize -> Vivado Crash

Crash report :
/----
Stack:
/opt/XilinxNG/Vivado/2014.2/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x89e6d9)
[0x7fc1445f46d9]
/opt/XilinxNG/Vivado/2014.2/tps/lnx64/jre/lib/amd64/server/libjvm.so(JVM_handle_linux_signal+0xad)
[0x7fc1445fa4cd]
/opt/XilinxNG/Vivado/2014.2/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x89b4f3)
[0x7fc1445f14f3]
/lib/x86_64-linux-gnu/libc.so.6(+0x350f0) [0x7fc16bf4d0f0]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_ippcw.so(zynq::ps7_v1_4::pcw::backend::xml::parser::parse_sdkgen(zynq::ps7_v1_4::pcw::backend::xml::xmliter)+0x7fd)
[0x7fc14a1140cd]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_ippcw.so(zynq::ps7_v1_4::pcw::backend::xml::parser::parse(char
const*)+0x365) [0x7fc14a115855]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_ippcw.so(zynq::ps7_v1_4::pcw::backend::global::loadxml(std::string
const&)+0x20) [0x7fc14a0dc840]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_ippcw.so(zynq::ps7_v1_4::zynq_config::ZTop::SDK_Initialize(std::list<std::pair<HSTString,
HSTString>, std::allocator<std::pair<HSTString, HSTString> > >&)+0x1a0)
[0x7fc14a159e00]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnExpToSDKImp::init_zynqDataModel(HRSBMoBlk*,
HDARPart const*)+0xb65) [0x7fc152735a15]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnExpToSDKImp::replaceZynqBlock(HXMLWElement*,
HRSBMoBlk const*, HDARPart const*)+0xb3) [0x7fc15274b5e3]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnExpToSDKImp::addModules(HXMLWElement*,
HRSBMoDesign const*, HDARPart const*)+0xc0e) [0x7fc15274c68e]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnExpToSDKImp::generateSDKXml(boost::shared_ptr<HXMLWElement>,
HRSBMoDiagram const*, HSTString, HDARPart const*)+0x586) [0x7fc15274cfe6]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnExpToSDK::exportToSDK(HRSBMoDiagram
const*, HSTString, HDARPart const*, HSTVector<HSTString,
std::allocator<HSTString> >&)+0x438) [0x7fc1527293f8]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnEngineMgr::exportHardware(HRSBMoDiagram
const*, HSTString, HDARPart const*, HSTVector<HSTString,
std::allocator<HSTString> >&)+0x76) [0x7fc1527198b6]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnProcess::runProc(std::vector<HRSBEnProcess::ExternalProc,
std::allocator<HRSBEnProcess::ExternalProc> > const&, HRSBMoDiagram*,
HRSBEnEngineMgr*, HSTVector<HSTString, std::allocator<HSTString> >*,
HRSBXlParamProp*, HRSBMoHierBlk*)+0x52a) [0x7fc152757cea]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnProcess::runProc(HRSBEnProcess::ExternalProc,
HRSBMoDiagram*, HRSBEnEngineMgr*, HSTVector<HSTString,
std::allocator<HSTString> >*, HRSBXlParamProp*, HRSBMoHierBlk*)+0x65)
[0x7fc152758a75]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnEngineMgr::generateDesign(HSTString
const&, HSTString const&)+0x1a5) [0x7fc15271a395]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnCompositeFile::generateTopHdlWrapper(HDGUIStatus&)+0x125)
[0x7fc1526ee845]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_rsb.so(HRSBEnCompositeFile::_generateFor_(HSTVector<HSTString,
std::allocator<HSTString> > const&, HDGUIStatus&, bool)+0x110)
[0x7fc1526f0310]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_filemgmt.so(HDDACompositeFile::generateFor(HSTVector<HSTString,
std::allocator<HSTString> > const&, HDGUIStatus&, bool)+0x153)
[0x7fc15606e263]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_tcltasks.so(HTCDesignGenerateTarget::execute(Tcl_Interp*)+0x80e)
[0x7fc147a7868e]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_common.so(+0x49679b)
[0x7fc16ce7a79b]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(+0x331f5)
[0x7fc167e3c1f5]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(+0x76bbe)
[0x7fc167e7fbbe]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(+0x7e767)
[0x7fc167e87767]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x77)
[0x7fc167e3e327]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_common.so(+0x496012)
[0x7fc16ce7a012]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(Tcl_ServiceEvent+0x87)
[0x7fc167eb0b37]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(Tcl_DoOneEvent+0x129)
[0x7fc167eb0e69]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_commontasks.so(+0x2b5d95)
[0x7fc164425d95]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_commontasks.so(+0x2be057)
[0x7fc16442e057]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_commontasks.so(+0x2b6033)
[0x7fc164426033]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_common.so(+0x49679b)
[0x7fc16ce7a79b]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(+0x331f5)
[0x7fc167e3c1f5]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(+0x76bbe)
[0x7fc167e7fbbe]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(+0x7e767)
[0x7fc167e87767]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x77)
[0x7fc167e3e327]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_commonmain.so(+0x6ee0)
[0x7fc16c7deee0]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/libtcl8.5.so(Tcl_Main+0x1d5)
[0x7fc167ea9175]
/opt/XilinxNG/Vivado/2014.2/lib/lnx64.o/librdi_common.so(+0x4c50c9)
[0x7fc16cea90c9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4) [0x7fc16ba020a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fc16bffdc2d]
\----

On debian jessie there are newer versions installed e.g. libtcl8.6
instead of the libtcl8.5. The
older version of some libraries are shipped by the tool-chain vendor
(xilinx) but I think there is
a conflict based on the libc6.

The problem has been reported on xilinx developer forum and there is
also a proposed solution.... installing
centOS in a jail... It is not really a solution more workaround... ;-)
Yes, I did some "google" lookup, first. The best results are linked below:
[1] ->
http://forums.xilinx.com/t5/Synthesis/Vivado-synthesis-fails-w-o-useful-error-message/td-p/497886
[2] -> http://threespeedlogic.com/blog/2014/08/07/vivado_debian.html


Does someone know more about the vivado 2014.2 issue? Is it the right
place, when I assign the bug to the eglibc6 maintainer
chain? Thanks for further advices and the time you spend while answering
to this question! I can provide more information to
the system etc. if needed! feel free to ask.

Best regards,
Andreas


Reply to: