Generate a .gdb.sh script that runs GDB for a failed test #5392
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm wondering it may make sense to generalize this, by allowing a general prefix to the sh script. E.g. what I usually do as first step is |
|
Maybe make the mode an argument to the script instead, that way we dont pollute the filesystem: ./001.sh gdb or ./001.sh valgrind etc |
beberlei
force-pushed
the
GdbShellScript
branch
from
315fd76 to
158cd2f
Compare
|
Merged in ec88bbc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This would be super helpful while developing as you could immediately get a gdb session for a failed test (if its a segfault for example). Example:
./Zend/tests/001.gdb.sh