AnsweredAssumed Answered

ModelSim SE 10.5f SIGSEGV

Question asked by marek_sotola on Jul 19, 2018
Latest reply on Jul 19, 2018 by Community_Admin

I'm running ModelSim 10.5f with Xilinx 13.2 on CentOS 7.5.1804.

 

Somewhere in my vsim run, I encounter a SIGSEGV. It looks like it has something to do with FDE.vhd, but nothing in FDE.vhd looks suspicious. Here's my stack trace:

 

# Attempting stack trace sig 11

# Signal caught: signo [11]

# vsim_stacktrace.vstf written

# Current time Thu Jul 19 14:34:03 2018

# ModelSim SE Stack Trace

# Program = vsim

# Id = "10.5f"

# Version = "2018.04"

# Date = "Apr 4 2018"

# Platform = linux_x86_64

# Signature = 6b480f24c92620d24b37ef6430ed527e

# 0 0x00000000005fb889: '<unknown (@0x5fb889)>'

# 1 0x00007fefeb0f3731: '/opt/Xilinx/13.2/ISE_DS/ISE/vhdl/src/unisims/primitive/FDE.vhd:52'

# 2 0x000000000064118a: '<unknown (@0x64118a)>'

# 3 0x00000000007de6dc: '<unknown (@0x7de6dc)>'

# 4 0x00007fefeabafd1c: 'hdl/vhdl/mult.vhd:143'

# 5 0x000000000064118a: '<unknown (@0x64118a)>'

# 6 0x00000000007de6dc: '<unknown (@0x7de6dc)>'

# 7 0x00007fefeab953b8: 'hdl/vhdl/pixelSearch.vhd:409'

# 8 0x000000000064118a: '<unknown (@0x64118a)>'

# 9 0x00000000007de6dc: '<unknown (@0x7de6dc)>'

# 10 0x00007fefe91764b4: 'hdl/vhdl/user_logic.vhd:1689'

# 11 0x000000000064118a: '<unknown (@0x64118a)>'

# 12 0x00000000007de6dc: '<unknown (@0x7de6dc)>'

# 13 0x00007fefe84592d1: 'hdl/vhdl/gnfir.vhd:830'

# 14 0x000000000064118a: '<unknown (@0x64118a)>'

# 15 0x00000000007de6dc: '<unknown (@0x7de6dc)>'

# 16 0x00007fefe8443344: '<full path omitted>/tb/tbsystem.vhd:189'

# 17 0x000000000064118a: '<unknown (@0x64118a)>'

# 18 0x00000000007de6dc: '<unknown (@0x7de6dc)>'

# 19 0x000000000086697b: '<unknown (@0x86697b)>'

# 20 0x0000000000852250: '<unknown (@0x852250)>'

# 21 0x0000000000852ece: '<unknown (@0x852ece)>'

# 22 0x0000000000c284ac: '<unknown (@0xc284ac)>'

# 23 0x000000000165b3ef: '<unknown (@0x165b3ef)>'

# 24 0x000000000165c5a9: '<unknown (@0x165c5a9)>'

# 25 0x000000000169ed6a: '<unknown (@0x169ed6a)>'

# 26 0x00000000016a789f: '<unknown (@0x16a789f)>'

# 27 0x000000000165d8c3: '<unknown (@0x165d8c3)>'

# 28 0x0000000001668754: '<unknown (@0x1668754)>'

# 29 0x000000000165c5a9: '<unknown (@0x165c5a9)>'

# 30 0x000000000169ed6a: '<unknown (@0x169ed6a)>'

# 31 0x00000000016a7bc0: '<unknown (@0x16a7bc0)>'

# 32 0x000000000165af93: '<unknown (@0x165af93)>'

# 33 0x000000000166da58: '<unknown (@0x166da58)>'

# 34 0x000000000165c5a9: '<unknown (@0x165c5a9)>'

# 35 0x000000000165d1f6: '<unknown (@0x165d1f6)>'

# 36 0x000000000165d576: '<unknown (@0x165d576)>'

# 37 0x0000000000dbd4e6: '<unknown (@0xdbd4e6)>'

# 38 0x00000000016b85c1: '<unknown (@0x16b85c1)>'

# 39 0x0000000001701961: '<unknown (@0x1701961)>'

# 40 0x00000000016ce07d: '<unknown (@0x16ce07d)>'

# 41 0x00000000016ce3b5: '<unknown (@0x16ce3b5)>'

# 42 0x00000000015592e6: '<unknown (@0x15592e6)>'

# 43 0x00000000009cb92e: '<unknown (@0x9cb92e)>'

# End of Stack Trace

 

Does anybody have advice on how to further debug this issue and/or proceed?

 

Thanks,

Marek

Outcomes