GDB current directory init file
Reported by
j...@nottheoilrig.com,
Nov 12 2016
|
||||||
Issue descriptionCould we automatically write a .gdbinit file with the following lines to the output directory (e.g. out/Default/.gdbinit)? > python > import sys > sys.path.insert(0, '../../third_party/WebKit/Tools/gdb') > import webkit > sys.path.insert(0, '../../tools/gdb') > import gdb_chrome
,
Nov 18 2016
I don't think it belongs to Infra - we do not control the details of tests. If you'd like this to be a generic feature in all of chromium builders, consider adding a corresponding step / functionality to chromium recipe. If that's the case, a better component is Infra>Platform>Recipes. Though I'm not sure if it should be at the recipe level - this still sounds a test detail to me.
,
Nov 18 2016
Actually, I think it would be better to automatically create chrome-gdb.py (e.g. out/Default/chrome-gdb.py). In that case all it need contain is: > sys.path.insert(0, '../../tools/gdb') > import gdb_chrome
,
Nov 21 2016
I have in mind something like the following [1]. What do you think? [1] https://codereview.chromium.org/2522523002
,
Nov 24 2016
,
Dec 21 2016
,
May 15 2017
This is definitely not recipes related in any way. Please find an appropriate owner on the chrome team (i.e someone in https://chromium.googlesource.com/chromium/src) to help you change this.
,
May 16 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Nov 14 2016