Uh oh!
There was an error while loading. Please reload this page.
do not include $FILENAME in globals - #1105
Conversation
`$FILENAME` is unsafe to include in the globals because it modifies ARGV and raises an error if it's a file that does not exist. This causes two issues if rdbg used to debug a command with arguments. * when using rdbg the server will crash when running `info globals`, as it does not catch the error * when using a DAP client that requests globals before the debugged program was able to handle its arguments then the ARGV changes and the program will not do what's expected
ko1
commented
May 30, 2024
Thank you! |
Launchable Report❌ Test session #2946090 failed ❌ Test session #2946091 failed ❌ Test session #2946093 failed ❌ Test session #2946094 failed ❌ Test session #2946120 failed Passed test sessions✅ Test session #2946072 passed Build: refs_pull_1105_merge_bb889708c935cc45b725629ceadecf0b2666927f |
$FILENAMEis unsafe to include in the globals because it modifies ARGV and raises an error if it's a file that does not exist. This causes two issues if rdbg used to debug a command with arguments:info globals, as it does not catch the error