Strace #8
Open
Strace #8
Conversation
This file contains 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
added 2 commits
November 24, 2012 17:32
… in your php error_log. Tried to follow idioms seen in previous snippets.
|
Note closed previous pull request as I needed to move this over to a topic branch on my remote once I added another pull request... I work on a quite large legacy application and I usually have to do some "software archaeology" to figure out the code's execution path. Besides grep, ack, ctags, etc., I find it useful to purposely print a stack trace at a place I know eventually gets executed, then simply open up the files in the stack dump. This snippet adds that capabilities using the snippet as such: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reissuing stack trace pull request from proper topic branch.