dynamic_cast_2

["Cabler, Adam" <adam_cabler at mentorg dot com>]

Title: Message

Hello,

I have a question about a core dump with Systemc on Linux. I have a Systemc design that runs great on Solaris, but when I try to use it on Linux, I get a core dump as soon as my code enters the constructor of the top level module. The stack trace show that this happens soon after the code enters __dynamic_cast_2 after sc_gen_unique_name. All of the examples that I have used work fine. The only difference is that I am linking in one of my libs to create an slib that gets loaded by another program. I will include some information below in case anyone else has had this problem.

Thanks,

Adam

libvia_soft.so => /mylib/lib/libvia_soft.so (0x400e2000)

libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40188000)

libm.so.6 => /lib/i686/libm.so.6 (0x401cb000)

libc.so.6 => /lib/i686/libc.so.6 (0x401ee000)

libpthread.so.0 => /lib/i686/libpthread.so.0 (0x4032a000)

libdl.so.2 => /lib/libdl.so.2 (0x40340000)

/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)