1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

bdebugger: why it doesnt go inside the "if" statement ?

Discussion in 'Support' started by AlexDeLara, Apr 9, 2015.

  1. AlexDeLara

    Joined:
    Apr 9, 2015
    Messages:
    3
    Likes Received:
    0
    Example:
    set abc=123 <- Line highlight is here
    if %DEBUG% equ 1 (
    set LOG=c:\temp\programTest_DEBUG.log
    call :mySub1
    call :mySub2
    ) <-- jumps here next time I press F11 or F10 and stays


    So, instead of going one by one, it wants to execute everything inside the if () however, I want the cursor to go inside so I can follow everything that is happening . What's up ? (or what's not up ? )
     
  2. thedave

    Joined:
    Nov 13, 2008
    Messages:
    253
    Likes Received:
    2
    I don't know why, but it's been this way forever (give or take), switch to IFF instead and you'll be back to debugging.
     
  3. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,022
    Likes Received:
    84
    WAD - an IF statement is always evaluated by the parser as a single line, regardless of how you format it in your batch file.

    If you want to step through each statement, use IFF.
     
  4. AlexDeLara

    Joined:
    Apr 9, 2015
    Messages:
    3
    Likes Received:
    0
    Ok, I had a feeling that the it was being evaluated as a single line statement would be answer . Thank you.
     

Share This Page