-
Notifications
You must be signed in to change notification settings - Fork 256
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
FR: add option to set source paths #418
Comments
See the other report: please help us reproduce this issue by providing a project we can compile that triggers this behavior |
The other issue is about handling stored debug info correct.
|
Ah I see, yes we should probably add some kind of path mapping or at least a list of source paths to query. |
Note: GDB comes with both |
kind of related to #450 - which is about binary data as both are easily stored for inspecting perf data later / on a different machine |
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
this patch add allows the user to add a custom source path which will overwrite the source path provided in the binary this makes the disassembler, ... work if the source code directory was moved after creating the binary closes: #418
Double clicking on a location in the callee/caller pane that has relative source file references I get the "failed to find file for location".
perf record --sample-cpu -z --aio --call-graph dwarf
I think this likely can be worked around using the configuration, but as my tinkering with that did not work out asking for help.
The text was updated successfully, but these errors were encountered: