-
-
Notifications
You must be signed in to change notification settings - Fork 739
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
Conversation
🤖 Coverage Update
To this point, this PR:
|
bfec296
to
be6ea9d
Compare
🤖 Coverage Update
To this point, this PR:
|
be6ea9d
to
b989829
Compare
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor stuff
a0e8af9
to
0473b0c
Compare
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
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.
0473b0c
to
45c7dac
Compare
🤖 Coverage Update
To this point, this PR:
|
🤖 Coverage Update
To this point, this PR:
|
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