Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[BUG] Get wrong tcl on Python 3.10 or lator with Windows

Aperta
  • Qualcosa non va?
#1,075 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
python
Ambito
testing

Direzione di ricerca

Start in vunit/sim_if/vsim_simulator_mixin.py at _source_tcl_file() and compare how the resolved testbench path and file_name are used; the report also points to _create_user_init_function() in vunit/sim_if/activehdl.py as a possible related case. Reproduce with the provided sample.py on Python 3.9 and 3.10, then check whether the generated Tcl uses the correct path and whether existing tests cover both simulator paths.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I found code seems to cause of this problem.
but I hesitate to commit code because I don't understand whole VUnit system,
and this is my first contribution for OSS.
so, I created bug report for someone else to fix this.

thank you.

Details

I put wave.do, the waveform window configure script of ModelSim on same directory of testbench.
and set vunit option modelsim.init_file.gui to $vunit_tb_path/wave.do in run.py.

then run test with CLI option -g | --gui, fail to execute script after GUI launch.
error message says script file C:/ProjectDirectory/C:/ProjectDirectory/tb/wave.do not found.
ofcourse, this is wrong path because of repeating C:/ProjectDirectory twice.

this problem only occurs Python 3.10 or later with Windows, but successed on 3.9.
(I don't know result with Linux)

Environment

  • OS: Windows 11
  • Python: CPython 64bit Windows (3.10 or lator)
  • vunit: 4.7.0

Reproduction

install CPython 3.9 and 3.10 to your Windows PC.

clone vunit repository on C:/WorkingDirectory, and change current directory to root of vunit repo.

PS C:\WorkingDirectory> git clone <url of vunit repo>
PS C:\WorkingDirectory> cd vunit
PS C:\WorkingDirectory\vunit>

create python code sample.py in current directory.

# sample.py

from vunit.sim_if import vsim_simulator_mixin as mixin

class config_dummy:
    design_unit_name = "sample_design"
    tb_path = "C:/WorkingDirectory/tb"

tcl = mixin.VsimSimulatorMixin._source_tcl_file(
        file_name="$vunit_tb_path/wave.do",
        config=config_dummy(),
        message="sample message")

print(tcl)

run sample.py with option to select Python version.

# Python 3.9
PS C:\WorkingDirectory\vunit> py -3.9 sample.py > 3_9.tcl

# or Python 3.10
PS C:\WorkingDirectory\vunit> py -3.10 sample.py > 3_10.tcl

here is diff of results.
- is 3.9, + is 3.10.

    set vunit_tb_path "C:/WorkingDirectory/tb"
    set vunit_tb_name "sample"
-   set file_name "$vunit_tb_path/wave.do"
+   set file_name "C:/WorkingDirectory/vunit/$vunit_tb_path/wave.do"
    puts "Sourcing file ${file_name} from some message"
    if {[catch {source ${file_name}} error_msg]} {
        puts "Sourcing ${file_name} failed"
        puts ${error_msg}
        return true
    }

wrong tcl created on Python 3.10.
tcl variable ${file_name} will evaluate as C:/WorkingDirectory/vunit/C:/WorkingDirectory/tb/wave.do.

Cause of Problem

I think the cause is a change of behavior pathlib.Path.resolve().

# on 3.9

>>> import pathlib
>>> pathlib.Path("$vunit_path/wave.do").resolve()
WindowsPath('$vunit_path/wave.do')

# on 3.10
# (current directory is C:/WorkingDirectory)

>>> import pathlib
>>> pathlib.Path("$vunit_path/wave.do").resolve()
WindowsPath('C:/WorkingDirectory/$vunit_path/wave.do')

so VUnit generates wrong tcl on static method _source_tcl_file() in vunit/sim_if/vsim_simulator_mixin.py.

# vsim_simulator_mixin.py

    @staticmethod
    def _source_tcl_file(file_name, config, message):
        """
        Create TCL to source a file and catch errors
        Also defines the vunit_tb_path variable as the config.tb_path
        and the vunit_tb_name variable as the config.design_unit_name

        """
        template = """
    set vunit_tb_path "%s"
    set vunit_tb_name "%s"
    set file_name "%s"
    puts "Sourcing file ${file_name} from %s"
    if {[catch {source ${file_name}} error_msg]} {
        puts "Sourcing ${file_name} failed"
        puts ${error_msg}
        return true
    }
"""
        tcl = template % (
            fix_path(str(Path(config.tb_path).resolve())),
            config.design_unit_name,
            fix_path(str(Path(file_name).resolve())),
            message,
        )
        return tcl

I think it will fix problem by removing resolve(),
but can't be sure there are no side effects.

tcl = template % (
    fix_path(str(Path(config.tb_path).resolve())),
        config.design_unit_name,
-       fix_path(str(Path(file_name).resolve())),
+       fix_path(str(Path(file_name))),
        message,
    )

P.S.

it might to occurs same problem for Actvie HDL.
see _create_user_init_function() in vunit/sim_if/activehdl.py.

tcl += f'source "{fix_path(str(Path(init_file).resolve()))!s}"\n' looks like occurs same problem,
if there are individual init_file for each testbenchs.
(I'm not Active HDL user, so this may be incorrect)

# activehdl.py

    def _create_user_init_function(self, config):
        """
        Create the vunit_user_init function which sources the user defined TCL file in
        simulator_name.init_file.gui.
        Also defines the vunit_tb_path and the vunit_tb_name variable.
        """
        opt_name = self.name + ".init_file.gui"
        init_file = config.sim_options.get(opt_name, None)
        tcl = "proc vunit_user_init {} {\n"
        if init_file is not None:
            tcl += f"set vunit_tb_name {config.design_unit_name}\n"
            tcl += f"set vunit_tb_path {fix_path(str(Path(config.tb_path).resolve()))}\n"
            tcl += f'source "{fix_path(str(Path(init_file).resolve()))!s}"\n'
        tcl += "    return 0\n"
        tcl += "}\n"
        return tcl
Lingua principale
VHDL
Stelle
850
Fork
305
Merge medio
2g 10h
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di VUnit/vunit

Tutte le issue di VUnit/vunit

Issue simili

Altre issue su Testing & QA

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.