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

'debugger_args' not honored for 'attach' configuration in gdb #206

Closed
rbrodeur opened this issue Feb 4, 2020 · 1 comment · Fixed by #316
Closed

'debugger_args' not honored for 'attach' configuration in gdb #206

rbrodeur opened this issue Feb 4, 2020 · 1 comment · Fixed by #316

Comments

@rbrodeur
Copy link

rbrodeur commented Feb 4, 2020

Additional arguments to gdb in 'debugger_args' are not being passed to the gdb command line when using the 'attach' connection method. In the embedded environment where I work, the '-x gdb.ini' parameter is required to set up gdb correctly to attach to the target. The 'autorun' configuration seems to happen too late and is not working in my environment.

It would be super helpful if the 'attach' connection method concatenated the 'debugger_args' the same way as the launch connection method seems to (note, I have not validated that the 'launch' method actually correctly concatenates 'debugger_args', I'm just looking at the code differences between launch and attach).

load():

const args = this.preargs.concat(this.extraargs || []);

attach():

if (target.startsWith("extended-remote")) {
    isExtendedRemote = true;
    args = this.preargs;
} else
    args = args.concat([executable, target], this.preargs);

Thank you for taking the time to create and maintain this vscode extension and thank you for your consideration.

@florin-saftoiu
Copy link

Same problem with the connect() method

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

Successfully merging a pull request may close this issue.

2 participants