Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Encounter terminated by internal(SEGV) error/signal

Status
Not open for further replies.

nooby

Newbie level 6
Joined
Aug 11, 2004
Messages
12
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
102
encounter terminated by internal

Hello all,

I am using SOC encounter v4.1 linux version ,when I finished TROUT, and then run optimiztion, the soc encounter will stop , and then report the error:
" Encounter terminated by internal(SEGV) error/signal ", Can anyone help me?

Thanks& Regards,

nooby
 

soc encounter segv

I am using NCSIM i was getting these errors in elaboration.
The SEGV errors are tipically genrated in following situation if systemC or C or C++ is used -
1. Null pointer assignment.
2. Not able to find symbol
3. The constructor or districtor defination is not proper or not defined.


Some solution are -
1. Define costructor or distructor properly.
2. Compile or gmake everytime with cleaning the work library.
3. Put asserts for checking Null pointer assignment.


I may help if you explain your problem a little bit more detail
 

encounter segv

I suggest you use another revision to try. when we used V4.1 on solaris, saw some strange peoblems and solved it using a new revision. sometimes the bug is case sensitive. V4.1 has several revisions for solaris.
 

soc encounter terminated by internal

Some solution are -
1. Define costructor or distructor properly.
2. Compile or gmake everytime with cleaning the work library.
3. Put asserts for checking Null pointer assignment.


I may help if you explain your problem a little bit more detail

Added after 2 minutes:

The SEGV errors are tipically genrated in following situation if systemC or C or C++ is used -
1. Null pointer assignment.
2. Not able to find symbol
3. The constructor or districtor defination is not proper or not defined
 

Hello

I have same sort of problems while invoking SoC Encounter. I tried the command "encounter -64 -simplefont" but got the same message.
Meanwhile my OS is RHEL6. Some people suggested me to use a previous version thought thats difficult for me as few more tools are running in this OS too.

Can anybody guide me get a way to use it without changing OS?

thanks
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top