How to debug tcl code in Hypermath module

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

I am trying to debug TCL code through hypermath tool in Hypermesh.

1.PNG.a7f6815f82b2f4c4c903b4aecfe2e063.PNG

But, i don't know why it doesn't work properly like other IDEs.

<?xml version="1.0" encoding="UTF-8"?>2.thumb.PNG.badb9a6fc343f33cb2a6dffadf9d58dc.PNG

I don't know how to debug it step by step, so that i can come to know the workflow. It doesn't even shows the values at breakpoints.

 

Any idea?

Answers

  • tinh
    tinh Altair Community Member
    edited August 2017

    Wow, it's very difficult to debug by this way.

    I usually debug by:

    - run tcl directly

    - read any error raised, it will show the error comes from which command, cause of error, and how the code should be

    - position the command, then fix it as bgerror handle advised

    never ever use other debugger. 

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2017

    Wow, it's very difficult to debug by this way.

    I usually debug by:

    - run tcl directly

    - read any error raised, it will show the error comes from which command, cause of error, and how the code should be

    - position the command, then fix it as bgerror handle advised

    never ever use other debugger. 

    Hey Tinh,

     

    Thanks for your reply. I was just wondering sometimes, i need to look into the workflow of the written code for enhancements. May be in that case i'd need some debugger to understand how is it working. Anyways, i'd be using the way you suggested because, this thing doesn't seem to work.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited January 2018

    I also meet this problem in v14 and v2017, the step in, step over, etc buttons are not working for *.tcl scripts, but seems works for *.hm files.

    I am wondering if this is something I didn't setup correctly or just a bug...?

  • tinh
    tinh Altair Community Member
    edited January 2018

    I see that, too. Maybe it's a bug.