<#754 Segfault in one of OpenLane's steps (or_repl...
# openlaneg
GitHub
12/09/2021, 9:29 AM#754 Segfault in one of OpenLane's steps (or_replace.tcl)
New issue created by progirep
Description
I'm getting a segfault in one of OpenLane's steps, but can't see what a possible reason for this could be (sorry, I don't "speak" TCL nor do I use docker for my own work - I'm only doing a few assembler styles, C, C++, Python, Java, some HDL, and CS Theory).
The project on which the problem occurs is a test project for integrating OpenRAM blocks into a design - it is a shortened version of the project at https://github.com/VLSIDA/openram_testchip.git using only two SRAM blocks.
Environment
The problem occurs both with the mpw-3a version of the workflow as well as with the "latest" (b911a5bbbcaa) version of the OpenLane docker images (selected by changing the respective lines in the files "Makefile" and "openlane/Makefile"). In the case of the "latest" version latter case, the gds.gz files in the gds/ directory of the project need to be gunzipped for the flow to reach the segfault. Also, when using the "latest" version, there is a warning for me that the PDK version is then not the right one - not sure if this is relevant because the segfault is the same.
Copy code
Python: v3.8.10
Kernel: Linux v5.4.0-91-generic
Distribution: ubuntu 20.04
Container Engine: docker v20.10.7
OpenLane Git Version: 2021.10.25_20.35.00
---
PDK Version Verification Status: OK
---
Git Log (Last 5 Commits)
commit e8f4a88f668b366f126bba40861153bf478a33c1
Author: Donn <me@donn.website>
Date: Mon Oct 25 20:32:41 2021 +0200
Last Minute Fixes for MPW3 (#675) Copy code
make user_project_wrapper