michael-hoke commented on issue #1297: URL: https://github.com/apache/daffodil-vscode/issues/1297#issuecomment-3144974455
This is due to us hard-coding the DFDL Parse started from the Execute TDML command to run instead of debug. In local testing, I was able to confirm that switching this to debug allows breakpoints to be hit during execution. I'm not entirely sure how we might want to go about fixing this. The obvious thing to do is to split the Execute TDML command into Execute TDML - Run and Execute TDML - Debug, but I'm not sure that's something we should do. I'm inclined to say that the process for debugging a TDML file would be to use the 'Debug Last File' command after executing the TDML once. The use case where this makes the most sense is when someone uploads a TDML zip to the user list asking for help and someone else goes to look at the parse contained in the test case. If they want to set breakpoints and step through right away, the extension currently wouldn't be able to handle that, and they'd have to Execute the test case (which would also create an infoset that could be compared to the infoset uploaded with the test case) then Debug Last File to step through and use breakpoints. It seems unlikely to me that an Execute TDML - Debug command would be all that useful because I think it would make sense to want to run first to create your own infoset because you'd want to see if the issue reproduces on your environment. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
