Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"stopAtEntry" option from launch.json is not respected #258

Open
ifarbod opened this issue Feb 27, 2024 · 3 comments
Open

"stopAtEntry" option from launch.json is not respected #258

ifarbod opened this issue Feb 27, 2024 · 3 comments
Labels

Comments

@ifarbod
Copy link

ifarbod commented Feb 27, 2024

Xmake Version

2.8.7

Operating System Version and Architecture

Windows 11 23H2

Describe Bug

When you start debugging, it will always stop at the target's entry point.

Expected Behavior

it should respect the option in launch.json:

    "stopAtEntry": false

Actual behavior, it doesn't.

Project Configuration

N/A

Additional Information and Error Logs

This is always true:

const debugConfig = { name: name, type: 'xmake', request: 'launch', target: targetName, stopAtEntry: true };

Is this intended?

@ifarbod ifarbod added the bug label Feb 27, 2024
@waruqi
Copy link
Member

waruqi commented Feb 27, 2024

this plugin do not use user launch.json, it will generate launch.json automatically. please set xmake.customDebugConfig to override it.

@ifarbod
Copy link
Author

ifarbod commented Feb 27, 2024

For anyone running into this issue, put this in your project specific settings.json

.vscode/settings.json

    "xmake.customDebugConfig": {
        "stopAtEntry": false
    },

@A2va
Copy link
Contributor

A2va commented Feb 27, 2024

If you start your debugging session by pressing F5, it will not use the launch.json, to use it you must use the Run -> Start Debugging menu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants