Fix "TclStackFree: incorrect freePtr. Call out of sequence?" bug

[abejgonzalez]

When running a large design (MegaBoomConfig w/ Larger L1/L2/LLC w/ Default Hwacha and different DDR3 setup), I get the following error "TclStackFree: incorrect freePtr. Call out of sequence?" and synthesis fails with no logs. Tracing back the issue on the forums seems to indicate that adding set_param synth.elaboration.rodinMoreOptions {set rt::extractNetlistGenomes false} solves the issue. In my case, it actually does fix the issue, and synthesis passes. I'm not sure what the impact is / what the flag does but when I have the chance I'll look into it and report back here.

Forum Post: https://support.xilinx.com/s/article/55687?language=en_US

[davidbiancolin]

I reported (what appears to be) the same error here: https://forums.aws.amazon.com/thread.jspa?threadID=346360&tstart=0l

I guess i'll follow up in that post with what you've found?

[davidbiancolin]

That's such an old issue -- it might just be this perturbs the build slightly so as to avoid the double free?

[davidbiancolin]

There should be other log files that are dropped in the directory in which the build script is run with stack traces. A few of them will be tcl wrappers detecting an error, but at least one of them should have an interesting stack trace. I've had teh best success capturing these when i ran the builds locally with -foreground set