Crash in Synopsys tools, why?

[hayoula]

Hi everybody,
Why do synopsys tools crash?
This is the crash log of Formality, I have similar log when other tolls of Synopsys crash:

Status: Building verification models...
Status: Processing Guide Commands...


The tool has just encountered a fatal error (SIGSEGV):

If you encountered this fatal error when using the most recent
Synopsys release, submit this stack trace and a test case that
reproduces the problem to the Synopsys Support Center by using
Enter A Call at https://solvnet.synopsys.com/EnterACall.

* For information about the latest software releases, go to the Synopsys
SolvNet Release Library at https://solvnet.synopsys.com/ReleaseLibrary.

* For information about required Operating System patches, go to
https://www.synopsys.com/support.

Release = 'C-2009.06' Architecture = 'amd64' Program = 'fm_shell'

'4250677 207838446288 5811876 5813958 5812890 5814247 5687538 8250759 8278782 8124034 6938702 6946654 6952648 5287776 4629961 4667450 4900431 4253719 9382223 30351567 34196031 34201698 34202543 30320577 30332375 30351567 34196031 34201698 34351849 34370886 34205796 34393832 30321195 4322462 207838370196'

Maximum memory usage for this session: 200740 KB
CPU usage for this session: 11.57 seconds

Thank you for using Formality (R)!

 

[iwpia50s]

The first thing I would try is to make sure I'm using the "-64" for 64 bit switch.

 

[hayoula]

Hi iwpia50s,

I have checked them for both 32-bit and 64-bit and almost in all cases the same crash happens.

 

[poluekt]

What does include your PATH variable? {Formality_dir}/tools/syn/bin ?

 

[hayoula]

Hi poluekt,
I cannot find any 'tools' folder in my Formality dir? Did you mean {Formality_dir}/linux/fm/bin?
I only have these ones incuded in mt PATH:
{Formality_dir}/bin
{Formality_dir}/linux/fm/bin

 

[poluekt]

In my ~/.bashrc
{Formality_dir}/linux/fm/bin

 

[yadavvlsi]

This sometimes happens. Just give a another run. If it is failing multiple times for the same run, EnterACall on solvnet.
Here is one article for understanding SIGSEGV error.
https://software.intel.com/en-us/articles/determining-root-cause-of-sigsegv-or-sigbus-errors/
https://en.wikipedia.org/wiki/SIGSEGV

 

[englishdogg]

i would also check if there are no errors or critical warnings that need to be looked into.. that at times are probable reasons for a fatal as well

 

[hayoula]

To englishdogg:
In many cases there is no errors or critical warnings when I have crash.

---------- Post added at 16:37 ---------- Previous post was at 16:35 ----------

Hi yadavvlsi,

I ran mutiple times, even I reset the system and still I have the same crash.

---------- Post added at 16:44 ---------- Previous post was at 16:37 ----------

Hi,
I checked again and I saw that I did not have SIGSEGV error in my PrimeTime crash,
Take a look please at PrimeTime crash log, it may help:

pt_shell> Initializing gui preferences from file /home/shahrokhi/.synopsys_pt_prefs.tcl
pt_shell> Loading db file '/opt/Synopsys/PRIMETIME/libraries/syn/generic.sdb'


The tool has just encountered a fatal error:

If you encountered this fatal error when using the most recent
Synopsys release, submit this stack trace and a test case that
reproduces the problem to the Synopsys Support Center by using
Enter A Call at https://solvnet.synopsys.com/EnterACall.

* For information about the latest software releases, go to the Synopsys
SolvNet Release Library at https://solvnet.synopsys.com/ReleaseLibrary.

* For information about required Operating System patches, go to
https://www.synopsys.com/support


Fatal: Internal system error, cannot recover.

Release = 'D-2009.12-SP1' Architecture = 'linux' Program = 'pt_shell'
Exec = '/opt/Synopsys/PRIMETIME/linux/syn/bin/pt_shell_exec'

'162325276 162325544 162325959 -6912 136190445 136191722 134695997 135084397 135089666 135090350 135184805 135071647 172040481 135185899 135126551 135186164 172040481 172150121 135129910 169111771 135678126 168648678 168649588 168650253 168872861 164296628 167434499 168040631 168657704 168873414 168045621 171955281 163961843 163983061 141101529 171954363 163971814 164397054 164392294 164536422 171950733 171951133 171959165 163960087 141043426 141034819 134596216 7888540'

 

[englishdogg]

looks like a time for some action on Solvnet / STAR in both your cases..
As a last check I would suggest to clear your environment settings just in case you have something that clashes with an internal variable.. I doubt that but worth a try.. Do you see this across other versions as well or only this one.

 

[nawaz.mjcet]

hi hayoula,
i'm also getting the same problem......did u slove it...if so please kindly share how to resolve it...
Thanks in advance.

Regards,
-Nawaz

 

[yx.yang]

I think it maybe your computer isn't powerful enough. Are you running your job on PC or server? What's the CPU of your server and the total physical memory you server has?
I think you may need try on a more powerful server.

 

[hayoula]

Hi everybody,
To englishdogg:
Unfortunately, clearing environment settings does not help.
To yx.yang:
I run these tools on servers: 1 has 8 cores and the other has 12 cores each one supporting 2 threads which makes it 24 cores logically. They both have enough RAM, I think.
So I think hardware is not the issue. Do you agree?:smile:

 

[yx.yang]

Hi, hayoula:
Is your synopsys tool crashd version, haha?
If not, you'd better ask the synopsys FAE for help.

 

[sam536]

Possible reasons for crash. check all these and send the test case to Synopsys if its valid license.

1. Many link libraries in link_path. If you have too many link libraries, some times tools will crash.
2. For any tool, -SP3 is stable version. Try with the different version and check.
3. Memory allocation need to check.
4. Dont start GUI initially.
5. Dont read SDB files for the first time and once all crash issues are resolved these can be read from next time.
6. CSH and SH also problem in unix. Need to pick the right path from the PT shell scripts.
7. Run with 64 bit machine in linux.
8. check the .db/.lib/.ddc written with different version ?. If yes, use the same version compatible with lib.



Suggest PT to run with 2007.06-SP3 . If it works fine, there is tool issue else variables you use with new version might be the problem.

Let me know if you are able to resolve the issue.

 

[nawaz.mjcet]

Hi, hayoula,
what is the formality version ur using....i had the same problem with 2010 version....but when are tried my design on 2011 version...it's not getting crashed...so try running ur design on latest version of formality.

Regards.
-Nawaz.

 

[hayoula]

Hi everybody again,
To yx.yang:
I tried different versions and I have the same problem. The situations were different, however.
To Sam:
Thanks for your advice. I will check your recommendations.
To Nawaz:
Good idea, but I don't have 2011 version. How can I get it?