We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From bruen...@google.com on February 03, 2011 14:44:57
we may want some options to control callstack formatting:
put file:line on same line as symbol: this is more the linux style, while the current format is more the windows style (gdb vs windbg)
print offset from symbol. that info is available on windows, and IMHO is very useful, esp to know how accurate the symbol info is.
Original issue: http://code.google.com/p/drmemory/issues/detail?id=290
The text was updated successfully, but these errors were encountered:
From bruen...@google.com on June 09, 2011 02:47:52
=> actually I already have -symbol_offsets option TODO: check whether having it on messes up suppress.txt generation or suppression matching
suggestion from Timur: print sym+offs only if don't have line #
Sorry, something went wrong.
From bruen...@google.com on August 29, 2011 09:55:21
Status: Started
From derek.br...@gmail.com on August 30, 2011 11:35:47
This issue was closed by revision r485 .
Status: Fixed
From bruen...@google.com on December 20, 2011 10:40:18
sym+offs when no syms is now issue #635
No branches or pull requests
From bruen...@google.com on February 03, 2011 14:44:57
we may want some options to control callstack formatting:
put file:line on same line as symbol: this is more the linux style, while the current format is more the windows style (gdb vs windbg)
print offset from symbol. that info is available on windows, and IMHO is very useful, esp to know how accurate the symbol info is.
Original issue: http://code.google.com/p/drmemory/issues/detail?id=290
The text was updated successfully, but these errors were encountered: