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

Fix gdb.execute not quoting paths #999

Merged
merged 4 commits into from
Sep 9, 2023
Merged

Fix gdb.execute not quoting paths #999

merged 4 commits into from
Sep 9, 2023

Conversation

Grazfather
Copy link
Collaborator

@Grazfather Grazfather commented Aug 25, 2023

Description

As I looked into #901, I found that we often don't quote filepaths in gdb.execute. This began lazy grep that tries to ID where we do this, and fixes where we can. Noticed that we cannot use quotes in the filename when setting up logging, so it instead restricts the logging path to one without spaces.

This is mostly untested.

Checklist

  • My code follows the code style of this project.
  • My change includes a change to the documentation, if required.
  • If my change adds new code, adequate tests have been added.
  • I have read and agree to the CONTRIBUTING document.

@github-actions
Copy link

🤖 Coverage Update

  • Commit: d6ce056
  • Current Coverage: 71.5741%
  • New Coverage: 71.5741%
  • Diff: 0.0

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@Grazfather Grazfather force-pushed the fix_gdb_execute_paths branch from bfec296 to be6ea9d Compare August 26, 2023 00:18
@github-actions
Copy link

🤖 Coverage Update

  • Commit: bba5f1c
  • Current Coverage: 71.5741%
  • New Coverage: 71.5741%
  • Diff: 0.0

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@Grazfather Grazfather force-pushed the fix_gdb_execute_paths branch from be6ea9d to b989829 Compare August 26, 2023 00:22
@github-actions
Copy link

🤖 Coverage Update

  • Commit: bba5f1c
  • Current Coverage: 71.5741%
  • New Coverage: 71.5741%
  • Diff: 0.0

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: f3287dd
  • Current Coverage: 71.5741%
  • New Coverage: 71.5514%
  • Diff: -0.022700000000000387

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: 528b630
  • Current Coverage: 71.5741%
  • New Coverage: 71.5514%
  • Diff: -0.022700000000000387

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: bba5f1c
  • Current Coverage: 71.5741%
  • New Coverage: 71.5741%
  • Diff: 0.0

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

Copy link
Owner

@hugsy hugsy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor stuff

gef.py Outdated Show resolved Hide resolved
gef.py Outdated Show resolved Hide resolved
@Grazfather Grazfather force-pushed the fix_gdb_execute_paths branch from a0e8af9 to 0473b0c Compare August 26, 2023 15:40
@github-actions
Copy link

🤖 Coverage Update

  • Commit: 46fba8b
  • Current Coverage: 71.5741%
  • New Coverage: 71.5769%
  • Diff: 0.0027999999999934744

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: 21ab515
  • Current Coverage: 71.5741%
  • New Coverage: 71.5443%
  • Diff: -0.029799999999994498

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: 46fba8b
  • Current Coverage: 71.5741%
  • New Coverage: 71.5769%
  • Diff: 0.0027999999999934744

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: 383f195
  • Current Coverage: 71.5741%
  • New Coverage: 71.5542%
  • Diff: -0.019900000000006912

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

hugsy pushed a commit that referenced this pull request Aug 26, 2023
This change makes it so that write hooks see the actual value provided
to a setting when `gef config` is used, and gives it the chance to raise
an exception if the value is invalid.

It also adds a validator 'no_spaces' and adds it to a few settings that
use filepaths, since we know (from #999) that some GDB commands
completely break when paths have spaces and/or when paths are quotes.
@Grazfather Grazfather force-pushed the fix_gdb_execute_paths branch from 0473b0c to 45c7dac Compare August 29, 2023 02:28
@github-actions
Copy link

🤖 Coverage Update

  • Commit: 644a11e
  • Current Coverage: 71.6614%
  • New Coverage: 71.6387%
  • Diff: -0.022700000000000387

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

@github-actions
Copy link

🤖 Coverage Update

  • Commit: 6a6e2a0
  • Current Coverage: 71.6614%
  • New Coverage: 71.6614%
  • Diff: 0.0

To this point, this PR:

  • does not include changes to tests
  • does not include changes to documentation
  • does not include forbidden words

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 this pull request may close these issues.

2 participants