Skip to content

thread-context refactor backtrace retrieval#3722

Closed
kares wants to merge 2 commits intomasterfrom
test-backtrace-refactor
Closed

thread-context refactor backtrace retrieval#3722
kares wants to merge 2 commits intomasterfrom
test-backtrace-refactor

Conversation

@kares
Copy link
Member

@kares kares commented Mar 10, 2016

historically there's createBacktrace2(int level, boolean nativeException)
... whose parameters are no longer used, proposing a getBacktrace() instead

getter name chosen since thread-context manages a backtrace state - does not need to create/generate one.

alternatively getBacktrace(int level) is added although we do not use the API.

kares added 2 commits March 10, 2016 14:32
... not really "creating" the backtrace - simply returning raw tracked backtrace elements
@headius
Copy link
Member

headius commented Mar 10, 2016

Are the "final" variable changes something your editor/IDE is doing? I don't mind it for new code but making changes like that in otherwise-unmodified code really messes up the diff.

Otherwise, this seems like a fine change and you should go ahead with it.

@kares
Copy link
Member Author

kares commented Mar 10, 2016

@headius yep, thanks - will try to tidy up the commit to avoid unrelated changes.

@kares
Copy link
Member Author

kares commented Mar 10, 2016

cleaned up: f060c79 and pushed to master

@kares kares closed this Mar 10, 2016
@kares kares deleted the test-backtrace-refactor branch March 10, 2016 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants