Thanks for the link. I'll respond there. We still have backtraces in our fork, so I'll continue using them for now. Ben had a good point though. I think for our use case, the last value is the one needed.
I don't think I can go into more detail other than we want to let the user navigate to where different things are set. -----Original Message----- From: Brad King [mailto:brad.k...@kitware.com] Sent: Wednesday, January 31, 2018 11:43 AM To: Rich Chiodo <rchi...@microsoft.com>; CMake Developers <cmake-developers@cmake.org> Subject: Re: [cmake-developers] Adding backtraces to every command Hi Rich, FYI there is discussion about providing backtraces from the server to clients here: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.kitware.com%2Fcmake%2Fcmake%2Fissues%2F17539&data=02%7C01%7Crchiodo%40microsoft.com%7C378e0befb60641901e2d08d568e2c87c%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636530245598201030&sdata=nVfucgI2ZfXqv519y8NNwj6yRtkdNw1PSw6o%2BBX9wuA%3D&reserved=0 It was originally done in CMake 3.10.0 but caused major memory bloat and so was reverted. > One of the things we need is to be able to get the location of where a > property is set. Threading that through everywhere for arbitrary properties will cause too much memory usage. `cmTargetInternals` already has dedicated fields for backtraces of specific properties. Something like that could be added for the properties you need. Can you provide more details about the use case? -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers