Community
Participate
Working Groups
When trying to debug issues it's often necessary to compare the contents of memory / variables / etc. between different targets being debugged. The pin button works for the variables view (for example), but doesn't work for the memory view when debugging more than one session. Steps to reproduce: 1) Create simple helloworld with some data to look at 2) Launch a debug session and open memory view 3) pin to debug context 4) launch another debug session 5) when you click between the session, the memory view As the memory view allows you to open multiple insances of itself, it would be useful to be able to pin one view to one debug context and another to another context. The memory browser seems to respect pinning, but doesn't seem to allow multiple browsers to be created. BRCM:TLFIREPATH-2231
Hi James, you should be able to open multiple instances of the Memory Browser, use the toolbar action beside the pin action. Is CDT folks still using the Memory view provided by the platform? I'll look into enabling pinning for this view if there is enough demand for it. Some minor changes in the platform memory view is required to support pinning, and than CDT can enable pinning.
(In reply to comment #1) > Hi James, you should be able to open multiple instances of the Memory Browser, > use the toolbar action beside the pin action. Ah, thanks Patrick! I missed that button.
The Memory View (as opposed to the Memory Browser) does not support Pin&Clone. We use the Memory View because of its ability to show multiple renderings (indeed, we have added our own custom rendering) and not having Pin&Clone support is a real problem. Is any action planned on this?
