Bug 484703 - TCF agent does not notify when unloading a symbol file
Summary: TCF agent does not notify when unloading a symbol file
Status: NEW
Alias: None
Product: TCF
Classification: Tools
Component: Agent (show other bugs)
Version: 1.4   Edit
Hardware: PC Unix All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Eugene Tarassov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-18 11:57 EST by christophe cleraux CLA
Modified: 2016-03-25 12:25 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description christophe cleraux CLA 2015-12-18 11:57:16 EST
When the TCF agent unloads a symbol file, because it has been rebuilt, it does not notify the user, and the the user is left alone trying to understand what happened.
Try this test case:
- build a process
- debug it
- do some stepping. So far so good.
- rebuild the process image
- do a step
- you are now in assembly mode !!

The unload of the symbol file is a good thing. After a rebuild, the debug info/text image may not be in sync with what is being debugged. TCF agent compares timestamps, and if they differ, the symbol file will be unloaded.

I request that an event is being sent on such situation, so a workflow could be provided to warn the user about this symbol file removal, so he will know why he's now in assembly mode.
Comment 1 Martin Oberhuber CLA 2016-03-25 07:29:38 EDT
We've run into this issue again, and it's a usability problem IMO ... could we get the additional notification sneaked into 1.4 (Neon) or does this look like a risky thing for any reason ?

CQ:WIND00-V7COR-3826
Comment 2 Eugene Tarassov CLA 2016-03-25 12:25:03 EDT
This supposed to work in opposite direction: the agent needs to be notified when application is rebuild while debug session is open. Time stamp check in the agent is a actually fallback, or workaround for missing notification from project manager. Extending this logic to provide user warning is rather kludgy approach.

The right way would be to implement better integration with project manager on the client side. It should warn user, notify agent with MemoryMap.set command, or close debug session. However, I don't know Eclipse project management code well enough to implement such code.