#945 ivl: pform.cc:390: PFunction* pform_push_function_scope(const vlltype&, const char*, bool): Assertion `scopex' failed.

devel
closed-fixed
nobody
None
5
2014-05-23
2014-02-05
Shai Lazmi
No

iverilog stops with the following message:
ivl: pform.cc:390: PFunction pform_push_function_scope(const vlltype&, const char, bool): Assertion `scopex' failed.
sh: line 1: 26711 Broken pipe /usr/local/lib/ivl/ivlpp -L -F"/tmp/ivrlg239106ca4" -f"/tmp/ivrlg39106ca4" -p"/tmp/ivrli39106ca4"
26712 Aborted | /usr/local/lib/ivl/ivl -C"/tmp/ivrlh39106ca4" -C"/usr/local/lib/ivl/vvp.conf" -- -
make: *** [tb] Error 134

iverilog version:
Icarus Verilog version 0.10.0 (devel) (s20121218-395-g607b63a)

System:
Linux Lablfs 3.12.0-10088-g2d3c627 #170 SMP Mon Nov 18 11:48:25 PST 2013 i686 GNU/Linux

this project is quite large but I have no idea what went wrong

Discussion

  • Martin Whitaker

    Martin Whitaker - 2014-02-05

    Without having the Verilog code that causes the error, it's going to be hard to debug this. Please could you run the compiler with the "-dscopes" command line option and provide a few lines of the output from immediately before the assertion failure. Hopefully this will show which part of your source code is triggering the bug.

    Please also let us know what (if any) other command line options you are passing to the compiler.

     
  • Cary R.

    Cary R. - 2014-03-01

    Like Martin said we cannot fix this without more information. It looks like a function scope is being parsed, but an enclosing definition scope (module/class) cannot be found. To help track this down try adding the following before the assert and see if this gives a clue to what/where the problem is.

    cerr << func->get_fileline() << ": problem with function " << name << endl;
    

    If this is not enough information for you to figure out the problem there are other things we can try.

    We will close this report if more information is not provided.

     
  • Cary R.

    Cary R. - 2014-03-01
    • Priority: 8 --> 5
     
  • Cary R.

    Cary R. - 2014-03-01

    For a number of reasons this does not qualify as a priority 8 bug so I am dropping the priority. Once we have more information we can reassess the priority.

     
  • Martin Whitaker

    Martin Whitaker - 2014-05-23

    It is likely this was caused by a function declaration outside a module. The latest code from git will output a sensible error message rather than the assertion failure. I'm going to mark this bug as fixed, but please reopen it if there is still a problem.

     
  • Martin Whitaker

    Martin Whitaker - 2014-05-23
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks